Why is BODS 3.2 Custom Dictionary Encrypted?

[brad_schroeter2]

I assume that the SAP-delivered dictionary PERSON_FIRM_EN is encrypted due to SAP considering it proprietary and not wanting users to extract/download the entries.

However, I don't understand why custom dictionaries created by the user needs to be encrypted?  Wouldn't it be useful to allow non-DS access to DS custom dictionaries, thereby having the dictionary in a central place (DS) but allowing other non-DS applications access to the dictionary table data?

Maybe I'm missing something here and other users can provide feedback.

Thanks,

Brad

[former_member229515 · Accepted solution]

Hi Brad,

The development team didn’t see a need to maintain two separate lines of code since we don’t document anything with how to modify the tables directly.  I contacted the Product Owner who will follow up with you.   There is work being done to integrate the content with non-Data Services applications with the next release of the product. 

A user can export all of their content into XML format and then could import it into another database structure.  It was expected that this would provide enough flexibility to utilize the changes outside of Data Services if so desired.

Thanks,

Matt

[Former Member]

Hi ,

The data is stored in encrypted format in dictionary table DC_[x]_PRIMARYENTRY i.e x means1..n. Could you advice how the data can decrypted?

Thanks,

Rahul

[paula_augedahl]

Rahul,

There is not a decrypt option specifically.  As Matt explained above, the custom dictionary contents created by you are exportable.  This would write the contents to an XML file in essence 'decrypting' the data so you can view it.  Else, if you want to see the contents, for DS 3.2, you can use Designer's Tools > Dictionary to browse the contents and for DS 4.0, you will use InformatioN Steawrd's Cleansing Package Builder to do the same.  This would not require an export of the data.

Thanks,
Paula

[Former Member]

Hi Paula,

I am attaching the dictionary xml for your reference. The primary name is showing in decrypted format which is highlighted in blue in the below screenshot. As per your previous post, data shoould have been in encrypted format, but in our case it is not likewise.

[paula_augedahl]

Rahul,

This screen shot suggests to me that your dictionary has an entry for ``` in it.  If you go into DS Designer and use Tools > Dictionary > Search and enter ```, do you get an entry back or do you get a message and if so, what is it (send screen shot)?

Thanks,

Paula

[Former Member]

Hi Paula,

As instructed I have searched in Designer> Tools > Dictionary > Search and searched the entry for  ``` which gave me the below result (screenshot attached below).

Please let me know the reason for this encrypted format entry that I am getting in Primary field.

[paula_augedahl]

Rahul,
It is not encrypted...it is simply the entry of ```.  It is just like an entry such as 'John' or 'Sr', etc.  Someone has entered the string ``` and classified it for parsing purposes.

The 'Classifications' box shows how the entry of ``` would be treated if it were found on input and passes a rule that is defined.

If ``` is not a real value you want treated in this manner, you can 'Remove' the entry from the dictionary.

Thanks,
Paula

[Former Member]

Hi Paula,

In continuation to your previous blog, I have created a new dictionary in BODS and have exported the dictionary into xml which is showing the same error/discrepency in the Primary field (i.e. encrypted in xml). Please refer below screenshots :-

Also I am attaching the exported dictionary xml below (exported after creating dictionary and its contents as per above screenshot):-

Please look into this and help us with any probable solution.

[paula_augedahl]

Rahul,

If you are telling me that you have only added this one change to your new dictionary and the data appears as ```````````````` in the exported XML, this will likely need investigation to learn the cause.  I have never seen this behavior with any data cleanse dictionary I have worked with. 

I would suggest logging a support case and providing the detailed steps you take to repeat this along iwth the versioning of Data Services and the Cleansing Package repository.  Screen shots showing this can be very useful.

Thanks,
Paula