Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Insert records into Recipient and Custom Table

sreev97350841
Level 2
Level 2

Hello,

We are using the Recipient table to store the customer attributes and also created a custom table to store several customer extension attributes. This is a 1:1 relationship.

I'm trying to insert records into the Recipient and the Custom table in a single workflow. Is this possible or do i need separate workflows for each Target dimension?

Any other suggestions on how to insert records into Recipients and the Custom table??

Thanks for your help

Sree

1 Accepted Solution
wodnicki
Correct answer by
Community Advisor
Community Advisor

Use reconciliation on key, or straight insert (no update) if that’s your use case.

View solution in original post

4 Replies
wodnicki
Community Advisor
Community Advisor

Hi,

Have the 'Update data' activity for nms:recipient output a transition, then connect it to a 2nd update activity for your custom table.

The outgoing transition will have the pk's of the upserted nms:recipient rows to use for your custom table's recipient-id fk.

If the relationship is the other way (recipient table has fk's to custom table), reverse the above order.

Thanks,

-Jon

sreev97350841
Level 2
Level 2

Thanks Jon.

I tried the approach and running into this error message. Do we need to perform any transformation before the 2nd Update activity?

06/26/2019 5:38:48 PM writer2 WKF-560029 The document types of inbound events ('srm:Custom' and 'nms:recipient') are incompatible (step 'Insert Recipients'). Unable to perform the operation.

wodnicki
Correct answer by
Community Advisor
Community Advisor

Use reconciliation on key, or straight insert (no update) if that’s your use case.

View solution in original post

sreev97350841
Level 2
Level 2

Straight Insert worked. I'll add the reconciliation step too. Thanks for your help