Skip to main content
Level 4
3月 6, 2019 7:23 午前 UTC

Get primary key of Recipient in Adobe Standard workflow - Query Activity

How to get primary of Recipient key passed to the next transition in Query Activity in ACS?

このトピックへの返信は締め切られました。

8 の返信

santhoshsrg作成者
Level 4
3月 6, 2019 7:24 午前 UTC

How to get primary key of Recipient passed to the next transition in Query Activity in ACS?

翻訳
vraghav
Adobe Employee
Adobe Employee
3月 6, 2019 11:05 午後 UTC

Hi santhoshsrg,

The PK value is automatically moved forward in the transition but if you will try to view it, it will appear as encrypted. It has been done to enhance security.

What is the exact use case?

Regards,
Vipul

翻訳
santhoshsrg作成者
Level 4
3月 7, 2019 10:06 午前 UTC

Hi Vipul,

I want to query a custom resource cusRes in query activity. The custom resource is linked to profile(recipient).

I want to pass the exact(Without encryption) "profile primary key"(cusRes/profile/id) to the next activity through the "ADDITIONAL DATA" section in Query activity. Is this possible?

翻訳
vraghav
Adobe Employee
Adobe Employee
3月 7, 2019 11:06 午前 UTC

Hi santhoshsrg,

Any reason why you wish to pass the ID of profile (linked to your cusResource?

If you fetch an attribute of profile schema inside the next activity, system is intelligent enough to make use of ID value to create an inner join.

Sorry of this is a redundant question but I'm trying to assist on your business use case.

Regards,
Vipul

翻訳
vraghav
Adobe Employee
Adobe Employee
3月 12, 2019 12:23 午前 UTC

Hi santhoshsrg,

Better to make use of customerID from CRM (if there is one). It will be a more relatable value which can be used across solutions.

Campaign PK value is not the right field to lookout for.

Regards,
Vipul

翻訳
santhoshsrg作成者
Level 4
3月 12, 2019 1:34 午後 UTC

Hi Vipul,

I have another case where i want to remove duplicate recipient records using Primary key in Deduplication activity. Kindly provide your feedback if this is feasible or not in Adobe campaign standard?

翻訳
prasannakumarmarru
Level 4
12月 3, 2019 4:50 午後 UTC

You will never have duplicate profiles based on primary key because primary key is always unique. I think you might have to deduplicate based on other field like email address.

Thanks!

翻訳