Hi everyone,
I'm seeking guidance on best practices for handling a specific scenario in Appian. Here’s the situation:
I have two records:
A1
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!
Discussion posts and replies are publicly visible
balti said:However, when deploying, I encounter an issue with missing objects.
Can you go into more detail here?
Need more details about these missing Objects (Those are mostly related to Actions that are defined on Record).Try Pushing all of the Related actions (PM), Interfaces and any Folders that are included ,within the same package
I'm asking about the relation, does appian restricts us to do what i explained above ? or getting data from such relation will result into any future problems
yes i agree, but I'm asking about the relation, does appian restricts us to do what i explained above ? or getting data from such relation will result into any future problems
here is the more information about relationship record A - column A1(pk) recprd B - column B1(pk), column A1(fk) relation in record A as one to many via A1-> A1(fk) - [using this throught the application for filtering, retriving data [less then 10 rowa] ] relation in record B as many to one Via A1(fk)->A1 - [using this throught the application for filtering, retriving data]
balti said:or getting data from such relation will result into any future problems
AFAIK , it will not cause any issue for you and there is no restriction.
Your use case is absolutely within the limits of Appian and there are no future issues to expect.
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!
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.
can you please provide me the source from where yo got this image?