Clientbase Online ID

[Michael Gumtow]

I'm currently investigating an issue we are noticing between rescard ID numbers between Clientbase Online and an on-prem database that gets synced from Clientbase Online.  Does anyone know if there is a table in Clientbase that can be used to obtain the lookup between the two different rescard IDs?

Thanks! 

[Dan Palley]

Hi Mike,

You should be able to use the Virtual Primary Key (VPK) which should be consistent across all database copies.

The Res Card VPK is made up of Create_DBGuidNo + Create_RecNo1.

Dan

[Michael Gumtow]

Hi Dan,

Thanks for the information.  So are you saying that the VPK is the Clientbase Online rescard number?  If not, how would we obtain the Clientbase Online rescard number from the VPK?

Thanks!

[Jeremiah Sellars]

Good morning Michael,

The VPK is not exposed by the API. You would have to run an SQL Select statement on your local database for the fields Dan mentioned. If the CREATE_DBGUIDNO is 1, it was created in the local Interbase database (your Primary database) and if any other value, the record originated from a copy database, i.e. CBO.

Can you let me know what agency you are with, Michael?

Thank you,

Jeremiah Sellars

[Michael Gumtow]

Hi Jeremiah,

I am with Fox World Travel.  We are in testing phases of implementing Clientbase Online, and we have an on-prem(primary) DB that syncs from CBO.  For example, we have a rescard number from the primary DB of 171090 with a create_dbguidno of 1 and createrecno1 of 171090, but in CBO the rescard number is 74200758.  Based on the provided information above, this doesn't seem correct.  Any other thoughts and/or insight on this would be greatly appreciated.

Thanks for your help!

[Dan Palley]

Hi Michael,

No the ResCard number is not necessarily the same as the VPK.  Unfortunately, the CB UI does not allow you to view or search by VPK.  I will forward this discussion to Jill Kuhns who is the product manager for ClientBase.

Dan

[Douglas Hammond]

This sounds like a common issue.  I've asked about this in the past via support with no solution as of yet.  The need to be able to cross reference rescards/invoices/profiles in the local db with CBO really seems like a must.  Very confusing experience for users and developers, CBO and backoffice users to have different record numbers.