Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
3 replies
Subscribers
7 subscribers
Views
1531 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hello all, I need to model a many to many bidirectional relationship.
octavianp
over 8 years ago
Hello all,
I need to model a many to many bidirectional relationship...which I know that is not available in Appian, but I am trying in some other ways.
The scenario is the following I have an application object which have two lists: list A and list B. In the interface I receive the application object through a rule input, and I have three sections:
- One editable grid for list A. This controls ri!application.A_list
- One editable grid for list B. This controls ri!application.B_list
- One editable grid for the link between them (this is basically a reproduction of the clasical many to many lookup table), which contains 2 dropdown fields, one for A one for B. This controls ri!application.A_B_list.
My initial ideea was to save in the A_B Link CDT the IDs of the entities A and B which are corelated. But this can not be applicable (or at least I was not able to do it), because at the moment of the creation, A and B entities do not have IDs. We need to...
OriginalPostID-170436
OriginalPostID-170436
Discussion posts and replies are publicly visible
Parents
0
octavianp
over 8 years ago
... first save them to the DB.
My second ideea was to save in the A_B Link CDT the entire A and B objects. This looked pretty good, but actually in the DB was saving 2 rows for A, and 2 rows for B. I suppose this is because of the one2many (application - A/B list) and one2one relationships ( A/B list - A_B_list).
Did anybody managed to find a workaround for this? Could you please help me with some examples?
Thank you,
Octavian
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
octavianp
over 8 years ago
... first save them to the DB.
My second ideea was to save in the A_B Link CDT the entire A and B objects. This looked pretty good, but actually in the DB was saving 2 rows for A, and 2 rows for B. I suppose this is because of the one2many (application - A/B list) and one2one relationships ( A/B list - A_B_list).
Did anybody managed to find a workaround for this? Could you please help me with some examples?
Thank you,
Octavian
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data