Nested CDTs vs Non Nested CDTs

Hi everyone,

I am trying to understand in terms of Appian's best practice as to which way to go when creating CDTs and maintaining their relationships, and the use of nested CDTs.  Is it recommended to use nested CDTs per best practice, or is it better to stay away from that?  From my understanding, it's easier and better to create the tables in the database first then create CDTs from db where the relationship is maintained strictly in db and not necessarily in Appian.  Then there is the other way, in which the cdts are created in Appian, with the relationships maintained through the use of Nested CDTs for the foreign key etc..  Is it a matter of preference to create the CDTs from db vs the other way with nested CDTs, or is it Appian recommended? 

Any thoughts on this?

Regards,

Jerry

  Discussion posts and replies are publicly visible

Parents
  • Hi Jerry,

    As others mentioned, while creating Nested CDT's, we need to check the below mentioned points:

    (1) What is the functionality? Can we avoid by proceeding with two or more tables referenced to each other? If not, can we create a complex view having the complete data. I prefer the Complex View. A CDT can be created mapping the complex view can be used in creation of Form(while Storing data), Summary Dashboards (while retrieving data), Records, Reports etc. This is simple and also effects the Performance.

    (2) If creating complex View is not feasible, Nested CDT approach can be used. But recommended Best Practice is to have it only for one level.

    Thanks,
    Farnaz
Reply
  • Hi Jerry,

    As others mentioned, while creating Nested CDT's, we need to check the below mentioned points:

    (1) What is the functionality? Can we avoid by proceeding with two or more tables referenced to each other? If not, can we create a complex view having the complete data. I prefer the Complex View. A CDT can be created mapping the complex view can be used in creation of Form(while Storing data), Summary Dashboards (while retrieving data), Records, Reports etc. This is simple and also effects the Performance.

    (2) If creating complex View is not feasible, Nested CDT approach can be used. But recommended Best Practice is to have it only for one level.

    Thanks,
    Farnaz
Children
No Data