- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2023 10:57 AM
I thought this would be simple and it probably is, but I've yet to come up with the answer, so I hope to find someone smarter than me to provide some guidance. 🤔 I've stripped down our actual requirements for simplicity sake.
Table A has the following fields: Company Name (display value, string), Company ID (string)
Table B has the following fields: Company ID (reference to matching Company ID record on Table A), Identifier (string)
Table A coalesce is on Company ID.
Issue: Using a Robust Transform, what is needed is that when a new record is being inserted into Table A, that reference is also established in the appropriate record in Table B.
We've had success in establishing the reference when the Table A record already exists, but not when the record is being inserted. The success came from querying Table A using a script (RTE Entity Operations, staging entity). The 'glide look up' option never seemed to return anything.
The simple path would be to go back to using standard transforms for this data, however we are trying to minimize the database operations as much as possible for performance reasons as the real-world implementation of this will be handling an extremely high volume, over 100 fields with data being applied to about 10 tables, all with varying references to each other.
If someone has been able to establish a reference between tables using a robust transform for inserted records, the community (and I, of course) would appreciate your wisdom! 😁
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2023 11:11 AM
Got it working!
Solution:
On the transform target field, dot-walk to the field(s) you coalesce on.
Example:
We mapped the following fields to the Stage entity: ID, Company Name, Identity
When mapping Stage to Company (Table A above), it's a straight-forward map. ID > ID, Company name > Company name
When mapping Stage to Ident (Table B above), this is where the dot-walk takes place. Identity > Identity Type, ID > ID.ID (in our example, the dot-walk is simple: u_id.u_id).
Note: the field that Stage > Ident targets is defined on the Ident entity. We named it ID with a path of u_id.u_id
This dot-walk represents the field of the unique (coalesce) in Table A. If there is more than one field being used to coalesce, map each one to ensure your reference is always pointed to the correct record.
Hope this helps save someone from going through the same long, painful process! 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2023 06:38 AM
Thanks for the response Vidya.. But It Didn't work out still !!
Thanks ,
Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 07:24 AM
Hello SRDan,
what exactly is in your payload (for Caller)?
Regards,
Marcin