Does automatic key generation is shared between nms:recipient and xtk:workflow

Avatar

Avatar
Validate 1
Level 4
DimaKudryavtsev
Level 4

Likes

43 likes

Total Posts

44 posts

Correct reply

10 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 25
Boost 10
View profile

Avatar
Validate 1
Level 4
DimaKudryavtsev
Level 4

Likes

43 likes

Total Posts

44 posts

Correct reply

10 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 25
Boost 10
View profile
DimaKudryavtsev
Level 4

29-10-2019

Hi, colleges!

I have noticed recently, that new nms:recipient records get assigned @id value over 300 million. Currently, the larges @id for this entity is 383,349,601 and it rising rapidly.

Obviously, we do not have so many customers, the real number is much smaller. I have done a quick investigation, and it seems that nms:recipient entity actually shares identity numbers with xtk:workflow and few others entities. When any of these records are created, the id is picked up from the same autoincrement value.

Now, problem is, we use a lot of sub-workflow or some temporary workflows, that gets spawn, executed and then deleted. We will have a couple millions of these created per day, so this auto-increment value will eventually overfill. What should we do? Is it possible to assign some custom @id to a workflow when spawning it, instead of picking an autoincrement value? Or Adobe will, actually, check if record with such id already exists before assigning it?

Thanks

Dima

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 50
MVP
Jyoti_Y
MVP

Likes

89 likes

Total Posts

123 posts

Correct reply

55 solutions
Top badges earned
Boost 50
Shape 1
Boost 5
Give Back 5
Give Back 3
View profile

Avatar
Boost 50
MVP
Jyoti_Y
MVP

Likes

89 likes

Total Posts

123 posts

Correct reply

55 solutions
Top badges earned
Boost 50
Shape 1
Boost 5
Give Back 5
Give Back 3
View profile
Jyoti_Y
MVP

29-10-2019

Hi,

If you are using autopk="true" or pkSequence="xtkNewId" then yes both tables are using same sequence.

To resolve issue of sequence filling up fast you can do:

1) Define custom sequence and use the same in your table. or

2) Find gaps in your sequence and point your sequence to start from that point.

Thanks.

Answers (1)

Answers (1)

Avatar

Avatar
Contributor
MVP
Raj_bounteous
MVP

Likes

90 likes

Total Posts

97 posts

Correct reply

32 solutions
Top badges earned
Contributor
Shape 1
Give Back 10
Give Back 5
Give Back 3
View profile

Avatar
Contributor
MVP
Raj_bounteous
MVP

Likes

90 likes

Total Posts

97 posts

Correct reply

32 solutions
Top badges earned
Contributor
Shape 1
Give Back 10
Give Back 5
Give Back 3
View profile
Raj_bounteous
MVP

29-10-2019

Hi,

If you are using sequence available in campaign, all the records that are generated across all the schemas use the same sequence and that might be the reason why you ended using using the sequence. we generally tend up using all the ID's for logging and running workflows temporarily which use the sequence. you can have custom sequence set up for the schemas that consume lot of ID's and there is some material available like the link below.

Sequence Auto Generation

Adobe Campaign: Sequences Exhaustion - Adobe Campaign Classic