11/25/2024 11:39:38 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 SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
|
|
|
|
SLX Unique Identifier Formats
Posted: 27 Jan 09 3:26 PM
|
I've been asked to renumber all of the unique identifier numbers in SLX.
So if our tickets start with 001-00-001477, I edit them to start at 101-00-001477.
I'm almost positive this is impossible, and should be impossible due to how relational database design works, but does anyone know more about this?
|
|
|
|
Re: SLX Unique Identifier Formats
Posted: 27 Jan 09 5:10 PM
|
All SalesLogix records have a Primary Key field, in the format tSSSSbbyyyyy, where:
t = a table identifier such as "t" for Ticket, "A" for Account, "a" for Address, and "Q" for custom tables.
SSSS = the site code of the database copy to which this record was first added
bb = Keybase, i.e. the generation of that database, in case it is a remote one that needed to be re-cut. It starts at A0 and can go up to ZZ with successive re-cuts.
yyyyy = a base-36 unique number, being the sequence for that sort of record on that table on that database copy. Runs from 00000 - 00009, then 0000A - 0000Z, then 00010 - 0001Z etc.
As that sort of key is not very user- or customer-friendly, SalesLogix has a means of translating it into a still-guaranteed-unique "pretty" format such as the one you show. This uses the PrettyKey function in Application.BasicFunctions (I think that's right - I don't cut code these days!)
In the case of Tickets, when a Ticket is added, they get a ticket ID as primary key, but then also run it through the PrettyKey function. The result is put into TICKET.ALTERNATE_KEY_PREFIX and _SUFFIX. When contatenated back together, that gives you the 001-00-001477 format. The 001 is generated uniquely from the site code, the 00 is generated from the keybase, and the last bit is from the unique number.
As this translation is done once and once only, on creation of the ticket, I see no reason why you couldn't later alter the leading part from 001 to 101 as long as there is no risk of you creating so many remote databases that one of them might generate a 101 value from its site code.
Personally, I think the safer way would be to not do it at all, or to replace the leading 1 with a letter.
Hope that helps.
Paul Roussell
Brisbane, Australia |
|
|
|
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!
|
|
|
|
|
|
|
|