BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
nhvdwalt
Barite | Level 11

Hi team,

 

We are getting the above error when working with various objects in MRM v7.1. Looking at the web log I can see unique constraint errors coming back from what looks like PostgreSQL.

 

Any ideas ?

 

Thanks,

1 ACCEPTED SOLUTION

Accepted Solutions
LOVE_SAA
Obsidian | Level 7

This causes when an object was loaded /created using data loaders. For example I have created a model 10005 as model id using data loader. Now when we try creating a model using GUI, for example it starts with 10000 as model id, second time when I create new model it increments to 10001 and so on . Now if I try creating a model to after 10004 the system increments to 10005 whereas we have already created 10005 using data loader. 

 

Hence unique constraint error takes place. Best practice while creating objects through data loader is  avoid integers and prefix with alphabets, for example M10005 or M-10005

View solution in original post

1 REPLY 1
LOVE_SAA
Obsidian | Level 7

This causes when an object was loaded /created using data loaders. For example I have created a model 10005 as model id using data loader. Now when we try creating a model using GUI, for example it starts with 10000 as model id, second time when I create new model it increments to 10001 and so on . Now if I try creating a model to after 10004 the system increments to 10005 whereas we have already created 10005 using data loader. 

 

Hence unique constraint error takes place. Best practice while creating objects through data loader is  avoid integers and prefix with alphabets, for example M10005 or M-10005