Hi,
I am very excited to announce the release of my book "Low-Code Application Development with Appian".
It will be available at the end of April and I can't wait to get your feedback. Meet me at Appian World Miami on Tuesday afternoon in the Community Hub to discuss all things Appian, low-code, and business process automation. I have a few discount codes I'd like to share with the you.
Find the book at Amazon: https://www.amazon.com/dp-B09SZ5V53W/dp/B09SZ5V53W
Happy low-coding,
Stefan.
Discussion posts and replies are publicly visible
Hi, I'm new here.
Thanks for the excellent book!
Is there a discussion group here to ask questions about examples in the book?
In particular, on p. 164, why do you choose a Many to One relationship when the ERM indicates a One to One relationship?
Hi Doug,
Thanks a lot for reading it :-)
My publisher and I are working on it. In the meantime, feel free to contact my by email (stefan@appian.rocks) and visit my blog (https://appian.rocks) for updates.
The design decision you mention was a tricky one. It was basically triggered by a limitation of one-to-one relationships in Appian records. This requires a unique field on both ends. And in this case, one of the fields is not unique. So I had to go with a many-to-one.
Fascinating!
Thanks again Stefan!