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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

NMSRECIPIENT.IRECIPIENTID Can we go negative ?

Avatar

Level 4
 
1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi,

in addition to what the others said, from my point of view going negative in schemas should be a warning sign. If you're consuming the positive integer range there is a good chance the negative range will be consumed as well at some point. If that happens, it will obviously be difficult to assign new ids. In this case you can only try to identify id gaps, re-arrange ids and re initialize the sequence to a gap that's big enough. This exercise can be extremely complex.

From my experience going negative could be a first sign of declaring an instance as end of life. I'd recommend researching why all ids have been consumed and switch off any process that causes it, to slow down id consumption.

Best regards, Tobias 

View solution in original post

3 Replies

Avatar

Level 3

Hello @Prasanna_Soni,

 

if it does not impact other applications around Adobe Campaign I do not see any inconvenience.

 

Br,

 

Amine

 

Avatar

Community Advisor

Hi @Prasanna_Soni ,

 

Yes, you can go negative if you have not used condition 'Primary key>0' in your workflows.

Or if you are willing to do changes in your technical workflows in order to go negative.

 

Thanks,

Jyoti

Avatar

Correct answer by
Level 4

Hi,

in addition to what the others said, from my point of view going negative in schemas should be a warning sign. If you're consuming the positive integer range there is a good chance the negative range will be consumed as well at some point. If that happens, it will obviously be difficult to assign new ids. In this case you can only try to identify id gaps, re-arrange ids and re initialize the sequence to a gap that's big enough. This exercise can be extremely complex.

From my experience going negative could be a first sign of declaring an instance as end of life. I'd recommend researching why all ids have been consumed and switch off any process that causes it, to slow down id consumption.

Best regards, Tobias