cancel
Showing results for 
Search instead for 
Did you mean: 

Is the Name to Code conversion broken?

GeorgeMcGeachie
Active Contributor
0 Kudos

A couple of years ago, someone raised an issue about the synchronisation of codes with names for models in a script, which I think is still outstanding (see https://apps.support.sap.com/sap/support/knowledge/preview/en/2213194).

I've recently had an issue with Name to Code synchronisation in scripts, and in the user interface. In my case, I'm trying to apply a pattern that forces the code of an entity attribute to include the entity code as well. That's easy to define, but the standard method for doing so (SetNameToCode) doesn't function reliably, and neither does the UI. I've had to write a script to do it manually for now. SAP Support agree with me that it's faulty, and have so far raised two Change Requests with Engineering:

- conversion script not applied to existing entity attributes; and %Parent.Name% replaced by model name - they've opened Change Requests 816278 and 816281

If you are at all affected by this issue (and I know some of you are affected in the PDM), please mark the following Knowledge Base articles as favourites, so you get informed about progress. If you scenario is not covered by those articles, please tell SAP Support.

Name to code synchronisation is a key feature of PowerDesigner, and fixing it should be a high priority for SAP.

Anyone with me on this?

GeorgeMcGeachie
Active Contributor
0 Kudos

I forgot to give you the Knowledge Base article IDs - here are the links:

2684575 - Conversion script is not applied to existing LDM entity attributes

https://launchpad.support.sap.com/#/notes/2684575

2684524 - %Parent.Name% defined in conversion script is replaced by model name

https://launchpad.support.sap.com/#/notes/2684524

GeorgeMcGeachie
Active Contributor
0 Kudos

If this issue is costing you time and money, you definitely need to tell SAP

Accepted Solutions (0)

Answers (1)

Answers (1)

thierry_despirlet3
Discoverer
0 Kudos

Indeed I also have the problem with PDM and DMM models using PD 16.6 SP6 PL05 !