11/26/2024 5:25:45 AM
|
| |
| 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!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
Integer Values for SLX IDs
Posted: 26 Sep 07 8:23 PM
|
What if I have turned on the autoincrement feature on a custom table but now I want to use integer values for the primary key instead of the standard SLXID (Char, 12)...
1) How do I set make the provider use integer values with the auto-increment?
2) What might i be concerned about? (E.g., mainviews built on that table?)
Hope someone can help.
|
|
|
| |
|
Re: Integer Values for SLX IDs
Posted: 27 Sep 07 6:55 AM
|
EZI,
Integer value key are not scalable. In the sense that they do not work with Remotes, and Mobile. To ensure that no key collisions occurr a key is required to be calculated based on various items. This distinction is made by the SiteCode which is a indicator of a unique system and the base 36 7 char incremented value. As you can imagine FFFFFFFF gives a greater range of values then 9999999.
IMHO except for legacy systems there is little value for using integer value primary keys.
Mark |
|
|
|
Re: Integer Values for SLX IDs
Posted: 27 Sep 07 12:15 PM
|
Ezi, are you being asked to provide a single strict numeric sequence over multiple databases, for something like pre-printed bank-check numbers? Or do you just prefer integer keys in general?
If it's a situation like pre-printed checks, where SLX is being used to fill in the amount and payee but the number is already printed on the check, one possible solution is to write a program that runs automatically before and/or after the sync server runs, and have that program be the only process that assigns (and therefore increments) the numbers. The check number (or whatever it is) won't be available immediately, but at least it will be strictly sequential.
If you know that all users are going to be connected to the internet when they process whatever it is that has to be sequentially numbered, and there's a webserver of some sort available, you could set up one of those neato XML web services to do it instead... That way everyone would get the number back immediately.
Either way, as has already been suggested, you should never try to use a simple integer as a primary key in a SalesLogix table... |
|
|
|
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!
|
|
|
|
|
|
|
|