EMN Export to use the Creo design ECAD_NAME and ECAD_ALT_NAME and the not the ECAD_HINT.MAP values
Please include detailed documentation such as screenshots, images or video.
1. What version of the software are you running?
8.0.8.0
2. What is the problem?
Reference ticket: 16962068
The ecad_hint.map file is being used as the default information to map our components (mostly as assemblies) while EMN files are being read out and written into Creo. However, if the design data is using a slightly different variant of the ECAD_NAME, Creo will STILL export using the name in the ecad_hint.map file. This should not be! It should use the name in the design file itself. Whenever the ECAD tool opens our EMN file, it gets flooded with warnings saying that the package name has a mismatch. We can't remove the component from the map file because we need the map file to map to the correct assembly model. If we put a wildcard ECAD_NAME "*", the ECAD tool still generates a warning:

The PCB designers can't read through hundreds or thousands lines of their warning log, trying to find the one or two changes they actually care about.
3. Are you using a workaround? If yes, please describe it.
No.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
If an ECAD_NAME or ECAD_ALT_NAME exists in the design file - it will use those values during export. If it doesn't exist, it will use the values in the map file.
On an EMN import, if the values do not match the design file, it will update from the EMN, with the understanding that the EMN is coming from the PCB team which is controlling that information.
This way, both teams have accurate ECAD_NAME and ECAD_ALT_NAME values and there will be proper collaboration without issues and warnings.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Our ECAD tool is getting errors about a mismatch to their cell names. It is causing confusion and spamming their warning log. The important information is now hard to see through these warning errors. Collaboration doesn't work well, causing an increase in unnecessary manual work (like creating separate PCB drawings) and human error.
