Record Relationships

Question

Hi everyone, 
 I'm seeking guidance on best practices for handling a specific scenario in Appian. Here&rsquo;s the situation: 
 I have two records: 
 
 Record A, with a primary key column named A1 . 
 Record B, with a primary key column named B1 . 
 
 There is a one-to-many relationship from Record A to Record B. I'm retrieving data of Record B using the 'relationship/related record data' from Record A, in both interfaces and expression rules. I've also defined the reverse relationship in Record B as many-to-one from Record B to Record A using the same column. 
 However, when deploying, I encounter an issue with missing objects. 
 Could you advise on the best course of action or Appian best practices for managing this type of relationship? Is there a recommended approach to avoid such issues in the future, or is there an alternative method for defining relationships? 
 Thanks!

Vinesh Gupta · Accepted Answer

Your point is while deploying cross related record for the first time both the record will through missing precedents error because both records relate to each other in this case the best way is two remove all the relations and related objects in record (view and action) and deploy and again deploy the same with older version with every relation intact. 
 correct me if I am wrong or if there is another, would love to discuss on that!

venkat Avuluri · Answer

What you are trying to say is Can we maintain relationships from both records(Inverse Relationship/Appian allows it) ?, Why not but if it's for single usage i don't recommend it . Do you have Usage for this Relationship in multiple places, go for it otherwise use query rules and expression rules to achieve it.

Record Relationships

Top Replies