I have created a Naming standards template and applied bindings. When I pull up physical tables, I see the template in the bindings. So far so good.
Now I want to "apply the naming". I assume you do this with the "naming utility". I pull that up, select the template on the first tab, navigate to the second tab, select the objects I want (tables, indexes, foreign keys, columns), and click "run translation".
Nothing is renamed in the model. Is this only supposed to be applied during Database Generation? It does not.
I know this must work, but I cannot figure it out. Also is there a better section to log this?
I figured this out. On the Naming Utility Options tab, I need to source from Physical, and Target to Physical. Then, when I clicked "run translation", it worked. My objects physical were renamed. In my opinion, so far, the "help" documentation is poor in this product. It is like many other products that documents what each option does, and few screenshots that show actual examples for real world scenarios.
I'm having the same problem in 18.4. I've created a naming Standards template to ensure that all physical names are UpperCamelCase, but can't get it to be applied at all. I've tried it in the LDM and PDM, with all combinations of source and target, but the names don't change.
I've bound all entities and attributes to the template, and also selected them in the Utility (why do I have to keep telling it which objects to apply the template to?)
LATEST NEWS - it DOES convert names if I say the Physical names should be in upper case, but it doesn't do CamelCase.
By the way, ddumas is right about the unhelpful documentation. The Help button on the Naming Standards Utility dialogue takes me to the information about the template - I can't find an explanation of the utility anywhere.
Next question - how do I get it to replace spaces with underscores?
How do I get the Naming Standards Utility to apply the rules to everything in the model, so I don't have to scroll down the list of entities, selecting every single list of attributes (which would be very annoying in a large model like the FIBO one I created recently)
Followed by confusion when later experiments in PDM generation had underscores appearing in physical names where they hadn't before, though naming standards template is still referring to UpperCamelCase
When defining your Naming Standards Template, you can define word separation on the General subtab of the Mapping tab. You can choose one separator (say, a space) for the Logical model Attribute Name, and a difference separate (say an underscore) for the Physical Column name. You can also choose to ignore, remove, or replace a list of special characters.
Select everything you want to apply the Naming Standards to before invoking the utility - doing this will cause it to preselect those items in the utility window. If you want all objects to be included, simply do a Ctrl-A on your model, then run the utility.
Thanks for this - I removed the Physical Word Separator (which defaulted to a space), and CamelCase was applied correctly. I shouldn't have to do that - I would expect a conversion from standard names (with spaces) to CamelCase to remove the spaces - isn't that part of the meaning of Camelcase? CamelCase is "writing phrases without spaces or punctuation"
Thanks again, if only the documentation told me that it would help.
Powered by IDERA