• State Suggested Answer
  • Replies 8 replies
  • Answers 3 answers
  • Subscribers 12 subscribers
  • Views 8134 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Best Practices

Nested CDTs vs Non Nested CDTs

jerrys790

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
  • 0
    A Score Level 1
    Hi Jerry,

    In addition to other comments, Avoid using nested CDT's until it is badly required. I just wanted to share my work experience. In all of the applications that I have worked on is maintain simple CDT's and the relationships maintained with just to point the foreign key constraints in the chain table. It is always better to go with create a DB object and then create CDT out of it.

    But few people may take the other approach like, creating the CDT and then create DB objects out of it. Most probably this approach might be used when you develop pretty new application from scratch. But we use to use this approach when we want to create some kind of POC applications which can be showcased to customers.
Reply
  • 0
    A Score Level 1
    Hi Jerry,

    In addition to other comments, Avoid using nested CDT's until it is badly required. I just wanted to share my work experience. In all of the applications that I have worked on is maintain simple CDT's and the relationships maintained with just to point the foreign key constraints in the chain table. It is always better to go with create a DB object and then create CDT out of it.

    But few people may take the other approach like, creating the CDT and then create DB objects out of it. Most probably this approach might be used when you develop pretty new application from scratch. But we use to use this approach when we want to create some kind of POC applications which can be showcased to customers.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.