Failed Data Integrity Check Err: 367 & 368

[LWSChad]

Hi,

As usage is increasing, I'm getting more and more ErrCode 367 & 368 / Failed Data Integrity Check.

 

I assume this is from the sequential nature of the PK Autonumber, but before I change all my tables to a different PK generator, please help me understand Random ID.

 

If I switch the PK from Autonumber to Random ID, will I still be able to maintain imported values, like I can with Autonumber?

 

Thanks!!

CHAD

[MayMusic]

Do you have a child and parent table? You need to make sure there is no orphan child in your child table. And to better understand how you can manage random ID it is better to create a small table and try to export and import it to see if you like the outcome. 

[ALittle]

Chad-

Curious what you decided to do? Maintaining imported values was my main concern with using random ID vs PK.

[RuisiHansamu]

Hello, just to share this. There is an updated forum post regarding this. You may find this helpful :