• State Verified Answer
  • Replies 1 reply
  • Subscribers 95 subscribers
  • Views 158 views
  • Users 0 members are here
Options
Related

Friendly named module GUID's are they supported?

Niels de Groot
25 days ago

I would like to know the support standpoint when using "friendly named" module GUID's
OOTB example: UID_AErole = QER-AEROLE-PERSONADMIN

My custom example: UID_AErole = CCC-AEROLE-PERSONADMIN
Is this supported?
And how about using "friendly named" module GUID's in other tables than AERole?

Regards Niels

  • +1 25 days ago

    At DialogTable, there is a flag via which our API defines where it allows a module GUID if necessary. If you assign it explicitly via script, this can also be a friendly-named GUID.

    select Tablename, IsModuleGUIDAllowed from DialogTable order by 1


    You can check the validity of a module GUID with the SQL function QBM_FGIGuidIsValid. The module GUID must not contain umlauts, diacritics, or Unicode characters. The recommendation is to use only plain ASCII characters A-Z, numbers, and the minus sign.

    select dbo.QBM_FGIGuidIsValid('CCC-AEROLE-PERSONADMIN')
--11
/*
0000 = 0: completely invalid
0001 = 1: valid, but no module, therefore as 8-4-4-4-12 e.g.: 933FE1DE-D1AC-4625-9D17-0665F022FBFC
0011 = 3: valid as MOD, but not convertible to normal GUID e.g.: MOD-CULT-en-US
0101 = 5: does not exist, would be a contradiction -> valid as MOD-32H but without module ID
0111 = 7: valid, MOD, Mod32H, but not transferable, e.g. MOD-0AEDE24A02C64BDC8E1AC8A14F509814
1011 =11: valid, Mod, ModSpecial, transferable, i.e. modules = db.ModuleOwner
1111 =15: Valid, Mod, Md32, transferable, i.e. Module = db.ModuleOwner */


    If you follow these rules you should be good to go.