Secondary INSERT Into a Mapping Table (Many-2-Many) When Authoring New Rows
Cédric BLANC
started a topic
over 2 years ago
Let's say I have three tables A, B, and C.
- Table A is a domain table (lookup table). - Table B is a many-to-many mapping table. - Table C is a regular table, containing a fuzzy matched entity.
When creating/editing a new record for Table C, I want to do an insert into Table B using a known ID from Table A, and the new ID from Table C.
The reason for this is because Table A is a type table and Table C can have multiple simutaneous types from Table A mapped to it.
Best Answer
C
Cédric BLANC
said
over 2 years ago
In the stepper for editing Table C you will include a Collection Step on the entity B. Once you have that, then you're able to add in the multiple simultaneous relationship types that you want.
But the key additional point that you may not have in mind is that there's a tab with explicit features to make it easier to handle many-to-many relationships. Tick the "Many to Many Relation" field, and you'll find that xDM makes it really easy to pick from the many values in Table A that you want linked to your new item in Table C.
1 Comment
Cédric BLANC
said
over 2 years ago
Answer
In the stepper for editing Table C you will include a Collection Step on the entity B. Once you have that, then you're able to add in the multiple simultaneous relationship types that you want.
But the key additional point that you may not have in mind is that there's a tab with explicit features to make it easier to handle many-to-many relationships. Tick the "Many to Many Relation" field, and you'll find that xDM makes it really easy to pick from the many values in Table A that you want linked to your new item in Table C.
Cédric BLANC
Let's say I have three tables A, B, and C.
- Table A is a domain table (lookup table).
- Table B is a many-to-many mapping table.
- Table C is a regular table, containing a fuzzy matched entity.
When creating/editing a new record for Table C, I want to do an insert into Table B using a known ID from Table A, and the new ID from Table C.
The reason for this is because Table A is a type table and Table C can have multiple simutaneous types from Table A mapped to it.
In the stepper for editing Table C you will include a Collection Step on the entity B. Once you have that, then you're able to add in the multiple simultaneous relationship types that you want.
But the key additional point that you may not have in mind is that there's a tab with explicit features to make it easier to handle many-to-many relationships. Tick the "Many to Many Relation" field, and you'll find that xDM makes it really easy to pick from the many values in Table A that you want linked to your new item in Table C.
Cédric BLANC
In the stepper for editing Table C you will include a Collection Step on the entity B. Once you have that, then you're able to add in the multiple simultaneous relationship types that you want.
But the key additional point that you may not have in mind is that there's a tab with explicit features to make it easier to handle many-to-many relationships. Tick the "Many to Many Relation" field, and you'll find that xDM makes it really easy to pick from the many values in Table A that you want linked to your new item in Table C.
-
Extend a model with new entities or attributes
-
Data types in xDM
-
Effective date on entities
-
Search using wild cards
-
Export a model from production and import on a development environment
-
"Allow Delete" vs "Allow Removal" privileges
-
LOV label in Named Query
-
Select location on a map and save coordinates
-
Is there a way to set up a master-detail relationship on browse mode?
-
Choose Either a Stepper or A Workflow Based on The User Privileges
See all 277 topics