On April 27, 2024, our Sign-in and Create Account options will be unavailable from 9am-12pm ET. During this maintenance window, developer account access and free trial registration will be unavailable.

GUID format different between DAPINODE and Oracle version of DTree

Hi,
I had an override in the Item Handler code (for product integration) where I need to get the category ID. The definition fragment passed into MapWFDataToCat() has all the information about the category including it's GUID except no category ID. So I wrote a small routine to fetch it from the GUID. In SQL Server, no problem. The GUID stored in the attribute definition (which comes directly from the DAPINode object) matches perfectly. However in Oracle, not so. In Oracle, if I have a GUID in DTree that looks like this:
FC147042998547079A2B26CFB9540773

the corresponding DAPI NODE will return this as its pGUID feature which is what gets copied into the attribute definitions GUID feature:
FC147042-9985-4707-9A2B-26CFB9540773

In Oracle is there a way to reconcile these besides stripping out the dashes? I would like to have just one function for all db vendors.
My Workaround was that I found that the auditInfo assoc passed in as another arg to the same function had the catID right there, but I don't know if it's universally going to always be there.
-Hugh