Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Discussion posts and replies are publicly visible
Did you consider to allow the selection of multiple desks when creating a new booking? Is the data model already a one-to-many for booking to desks?
Hello Stefan,
First of all, great book, and I'm waiting for the next publication of yours.
Actually, that is something I did not think of. So instead of acting on the Desk recordType, we would create a new Booking recordType instance, which would then accept an array of identifiers for selected Desks, Got it. We just need to make some adjustments in the data model. Does it sound like the way to go?
Thanks a lot. Check out my blog at https://appian.rocks for more content and updates on the book.
As you have to deal with a relational database, you cannot store a list of IDs in one fields. Consider to create a data model like this.
DESK <1-*> BOOKING-ITEM <*-1> BOOKING
This is similar to an order and order items.