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 Definitionwith 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.