Annotations in data-sharing features - bug?

[pausob]

Hi, using Creo4 here and I am wondering if I am doing something strange but this was not quite expected:

I prepared an explanatory note that is attached to geometry that is being brought in via the extern-copy-geom mechanism.

But the parameters displayed by this note, which show up just fine when viewing the source model, disappear when the note is rendered in the target model:

How the annotation and published geometry was prepared in the source model

What the published geometry looks like in the target model

I realize that to get around this *** issue, I can craft my note to only use its own "annotation element" parameters.  And via relations, those can be made to be equal to the "original" feature and model parameters.  But that seems like twice the work...

[tbraxton]

I do not think this is a bug. Including the AE in the pub geom probably does not carry with it the parameters (I am assuming model parameters) from the source model. Inheritance features support passing parameters using the varied items functionality. Another option would be to use a notebook (.lay) which makes global parameters available to any model declared to it.

In the target model if you create a test relation and attempt to use one of the missing parameters by selecting it in the relations editor, are any of the missing parameters available through the relations editor UI?

[pausob]

Yeah, in this case, I was simply looking to send the note to the target model(s).  So I was wondering if there is an option of packaging my note "as rendered".

I appreciate there are other ways of sharing up-stream-source information but it does seem that Creo software makes such things difficult and unintuitive.

Similar gripe to model dimensions, really - the system is not able to "package" the existing (driving) dimensions into the publish-geom feature so one is forced to make "duplicate" annotation elements and absorb those into the published geometry - 2x the work...

[tbraxton]

Is the AE (note) part of the assigned to the default combination state in the source model? I think the default state has all annotations assigned to it but that could come into play if somehow it is not part of the default combination state.

It probably is not possible with a copy/geom or pub geom. The introduction of inheritance features was meant to address the ability to propagate more than just geometry to another model. They predate combination states by many years, and I am not an expert on the nuances of how combination states work in practice.