I have two address records (not many in the scheme of things) that have an entity ID that starts with the letter "S". What entity is that or is this some hand rolled data someone put in for testing? It appears to be a valid ID, but I can't seem to figure out what entity it belongs to.

Jeff

Hey Jeff,

Did you already check the SITEKEYS table for entries that begin with an "S"? I'd start there, but I don't recall ever seeing an ID scheme that starts with "S" before. I'd guess it was hand rolled.

The S is for SQL  (Not sure what Table that would be), but this is based on the SlxIdGenerator class from the Web Client:

AddKeyMapEntry("SQL", TableIdType.idSQL, 'S', "SQL");

Here is the full Map of Tables:

USERSECURITY U

ACCOUNT A

OPPORTUNITY O

CONTACT C

ASSOCIATION B

ACTIVITY V

HISTORY H

EVENT E

USERNOTIFICATION n

PROCESS P

RESOURCESCHEDULE r

SECPROFILE F

SECRIGHTS I

SECENTITY N

SECTRANS T

AGENTS K

LIBRARYDIRS D

LIBRARYDOCS d

RESOURCELIST R

LEADSOURCE L

COMPETITOR Z

PRODUCT Y

ADDRESS a

OPPORTUNITY_CONTACT J

USEROPTION v

OTHER Q

QUOTA q

SQL S

JOINDATA j

PLUGIN p

PICKLIST k

SLXBUNDLE b

TICKET t

CONTRACT c

PROCEDURES X

RMA m

DEFECT f

ATTACHMENT Q

TEFFILE Q

SEC_FUNCTIONOWNER W

PRETTYKEYGENERATOR x

Look in the join data table to see what "other" tables are linked with the address field you are looking at.

Then scan the related tables for the ID's in question.

Either you exceeded the "Q" ID's list and then it moves through a list, that i can't remember, and you'll find the key in another table or its bugus data.

If its in the address.entityid field, it could be from several tables or customizations (joindata will tell you)

If its the addressid field itself, then you've exceeded the Q key and moved to the "S" or is bogus

Doh! Been so long I forgot about the "KEYDESC" column in sitekeys. I did look at the table and looked at KEYTYPE and ignored KEYDESC. There is a record for "S" in theKEYDESC column with a KEYTYPE of 11. I have no idea what 11 maps to, though.

Because I could, I wrote a quick console app that loops through every table in information_schema and had it generate a single ID for that table. None returned an ID that started with an S. Odd, since it's in sitekeys.

At least I know I can ignore it.

Jeff

Raul,

Interesting. You posted as I was writing my app. Curious as to what it's used for. I used QueryExpress to run slx_dbids("SQL", 1) and sure enough, it came back with an "S" ID.

Thanks,

Jeff

When SalesLogix generates IDs, it doesn't match to the Sitekeys based on the KeyDesc column, but rather on the KeyType.

Internally it keeps a Table (or enumeration) that lists the known Tables and their Key Types.

So, if a you want a New ID for the Account Table, it checks the list and figures out that the KeyType will be 1.

If the table doesn't have a matching value, it defaults to KeyType 25 (Other).

My Sitekeys also has an Entry with KeyType 11 that has a KeyDesc of S, however that entry is for the SECPROFILE table, and its ID prefix is "P" not "S".

As shown on the Table I built from the Web Client, KeyType 27 is associated with a table name called "SQL" (which I can't find anywhere), and that shows to have a Prefix of "S".

That said, it is always possible for someone to Generate Such ID manually to avoid conflicts during some sort of Data Manipulation.

I have done so myself when Merging Data from multiple DBs with the Same SiteCode, or when having to copy a given row.

The Reason for the Prefix is for Consistency and Order, but there is no Constraint that forces a given table to use a Given Prefix.

Try this code on your SalesLogix Windows Client:

MsgBox Application.BasicFunctions.GetIdFor("SQL")

  The returned ID will begin with S.   This is the response I got on my system:  S6UJ9A000001

Also, right after running this code, a new Entry got added to my SITEKEYS table with KeyType = 27 and KeyDesc = "S" (now I have two rows with S as the KeyDesc, but as described above, SLX doesn't use the KeyDesc for ID Generation).

I'm familiar with sitekeys and it's purpose but I'd just never seen the "S" before and couldn't figure out where it came from. I wasn't familiar with the SlxIdGenerator  - I haven't worked much with the SLX web version that uses it (actually any form of SalesLogix) for several years. We have a new customer that's on SLX but moving to MS CRM and I'm doing data mapping and that "S" ID threw me for a loop. Since I only have two records that are "S" IDs I'm going to ignore them.

Jeff