Hi!!!
Thanks.
Discussion posts and replies are publicly visible
My perspective on this is, that the database is only a integrated system like any other. Appian at its core does not need a relational database and the platform tries to limit dependencies on these integrated systems.
I am building enterprise Appian applications for > 12 years now and try to keep the relational DB as dumb as possible. And I never had the urge to do more than a simple view or a stored procedure for ETL jobs.
Low-Code with Appian gives you the opportunity to make the whole development a lot easier. Give it a try.
This is just my humble opinion and there are other perspectives on this.
I think the reason is that Appian is trying to be data-agnostic. It wants you to be able to form connections however you want, and if you should want to configure the connections the way they are in the database, great! Since records are sort of read-only at this point, I don't think there's an urgent need to force constraints on views. You're just attaching things together however you choose in order to look at them. No harm if you don't need the FK in order to get the views you want. It's actually kind of nice that Appian isn't forcing your hand.
I think that it may come into a problem when you're trying to write to tables that have FK constraints that have to be maintained, but for now you have to use CDT to write to datastore anyway. You can't use records for that. This is good, because CDT's do collect the foreign key relationships correctly.