BookmarkSubscribeRSS Feed

Dear SAS teams,

 

Request:

I would like to propose to include a simple spell check in the BDN web application, during the creation of a Term, to align with other checks across the BDN app.

 

Details / Problem:

 

When exporting a Term Definition with spaces an error message is displayed saying that the Term is not valid since the entity type may be max 23 characters". And this is correct.

As documented in the Business Data Network User Guide, Export Terms to an Entity Definition creates an entity definition file suitable for import to Master Data Foundation projects or SAS MDM. As such, it must meet the requirements in MDM as stated in the SAS MDM Administrator's Guide.

Note: Because of the addition of relationship type attributes, values in the MDM_REL_TYPE table must be sized to 23 characters or less to run the schema evolve process successfully. If you have values in the MDM_REL_TYPE table larger than 23, change the column size before attempting to run the schema evolve script. Only the underscore special character is allowed. Remove any other special characters in the MDM_REL_TYPE table before attempting to execute the schema evolve script.

But the process to create a term allows spaces and other chars.

 

Export to XML is a workaround, but still only a workaround for a functionality that is already implemented, the Export Definition.

 

Thank you in advance for your attention. I would like to hear the progress about this feature/hotfix request.

Kind regards,

Juan

 

 

4 Comments
Lisa_SAS
SAS Employee

Hi Juan,

 

I am looking into this further but I would like to clarify the behavior with you in more detail to be sure that I understand the details of your request. 

 

Business Data Network offers two distinctly different types of Export.  Export to an XML file is different and not interchangeable with Export Terms to an Entity Definition.

 

Export Terms to an Entity Definition is specifically designed for exporting terms into an Entity Definition file that can be imported into Master Data Foundation projects or SAS MDM.  The output file is a .met file which is not suitable for import into Business Data Network.  It can only be imported to SAS MDM. 

 

Given this specific use case, it may not be feasible to add a spellcheck or verification for term creation which would impact all terms being created regardless of whether they are for MDM usage or not.  It would likely require a configuration option be added in order to avoid warning on every term creation for installations where MDM is not installed or in use.

 

Can you provide more details on how Export to XML was utilized as a workaround? 

 

Please confirm my understanding and I will create a feature request for this item. 

 

 

 

 

 

Lisa_SAS
SAS Employee

Hi Juan,

 

Please respond back if you are still interested in pursuing this as a possible feature request.  

 

Regards,

Lisa

JuanS_OCS
Azurite | Level 17

Hi @Lisa_SAS,

 

thank you for your asnwers. Sorry for my lack of response, I just came back from holidays.

 

I will ask the customer about it and come back to you.

 

Regards,

Juan

Lisa_SAS
SAS Employee

Thanks for the update Juan.  I look forward to their feedback.