Problems faced while moving CustomTable Data through content staging

Naresh Ede asked on November 20, 2017 06:52

Hi Guys

I have a Custom table in both DEV server and Production server , I had added records in DEV custom table , and the record are tracked in staging tasks.

First time i Synchronised the records , all records moved to Production server.

Later i made some changes to already added records in DEV Server and those are also tracked in staging tasks, So i simply synchronised .

Actually i had developed a custom webpart to display records, and it works fine before ; After second time synchronisation the custom web part was broken and the same webpart works perfect in DEV environment.

So i want to know how the custom table data was synchronised and why i was getting the error.

what should effect if i was synchronised the updated records in staging tasks.


Naresh Ede

Recent Answers

Brenden Kehren answered on November 20, 2017 16:16

If you are using the Primary Key of the custom table as an identifier, this could be a problem because it could be different if you manually add content in both environments. I'd suggest adding some sort of code name for that record to store with your other queries or foreign key relationships.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.