Component name changes after running macro

[Inch]

We switched to NX8.5 this year and back when I was testing it I recall having the problem I'm going to describe and resolving it. But now its come back to bite me again and I can't recall what the solution was.

When I open an assembly part the ANT looks like this:

We have a macro (a real macro, not a journal) that makes some small modifications to a CAM object (operation or tool or whatever), it does absolutely nothing regarding assemblies. BUT after executing this macro the ANT now looks like this:

You can see that the descriptive name has < and > around it and the component name has underscores ( _ ) around it (the yellow highlight was added by me).

This isn't a problem until the user wants to run an application I wrote that does work with the components. At this point it gets the component names from some attributes and tries to find the instances of these components. Only now the component names have changed it fails to find them.

What the hell is changing the component name and descriptive part name??? And why???

Like I say I'm sure I found some setting or something regarding this a few months back, but I'm damned if I can find anything now.

[cowski1 · Accepted solution]

If Preferences -> assembly -> descriptive file name is set to something other than "file name", you will get the angle brackets around the name.

Perhaps the macro is inadvertently changing the file name option.

[Inch]

Well, that was it.
I now just have to work out why executing my CAM macro changes this setting!?!?!

[Inch]

The header of the macro I was talking about had the descriptive file name setting recorded into it. Not sure how, it just must have been set wrongly when the macro was recorded.
I just deleted that line from the macro and BOOL it worked!

Thanks for pointing me in the right direction @cowski1