Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Saturday, June 28, 2025 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Web Forums - SalesLogix Web Platform & Application Architect
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix Web Platform & Application Architect | New ThreadView:  Search:  
 Author  Thread: How to increase Site Keys in Saleslogix?
mark
Posts: 70
 
How to increase Site Keys in Saleslogix?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Dec 11 6:25 AM
fiogf49gjkf0d


Hi All,


 


I have Migrated data from Production SLX to QA SLX Recently in my Project and after two days i am getting error almost on insert of every record in very entity that "Primary Key Violation Error".


 


After some research i came to know that i have to increase my sitekeys through DB to over come this Error.


 


But I am not getting how to Do that?


 


 


Please Kindly Help me as early as possible so that i can resolve this issue. I am also Getting this error some times on production but almost every time when i bundle some data from produciton and put it in QA.


 


Please Help :smileysad:


 


Thanks,


Mark


[Reply][Quote]
Nick Hollis
Posts: 549
Top 10 forum poster: 549 posts
 
Re: How to increase Site Keys in Saleslogix?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Dec 11 6:55 AM
fiogf49gjkf0d

You should be creating new records as you move them across, and using the provider to get yourself a new id. This will automatically update the SiteKeys.


Whatever your import routine is, I would scrap it and change it to the above model. Remove any records already brought across and start again.


You could fix this manually you could get max(id) from table, add one 'hex' value to it and whack that value in sitekeys. Unsupported of course. Best course is to remove the data and start again properly.


Another approach is as you move the data across change the four character site key part of your id to something like 'QAXX'. This will mean you wont get a viloation with existing data, and you wont get a primary key violation when new records are added. You will need to be careful if you try to move the same record over again though (which to be fair you would have anyway).

[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 6/28/2025 2:13:35 PM