Hello,
I am having an issue with tagging of compoentns in one of assembly. I wanted to tag each pump with (Annotate-Notes-Leader Text) in Assembly. Now when edit the number of pump (it's in pattern) it miss the tag when I make it 2 to 4 and then 4 to 2 pump.
is there any way where it stay intact?
Hi @bhavik4244. I'm not sure I understand the situation, so just to clarify...
It sounds like you have a pattern of 'pumps' in an assembly, each with a 3D annotation leader note attached to it. Then when you change the quantity of the pattern to fewer, you loose the notes that were attached to the pumps that are no longer there, right? And when you add to the pattern quantity those notes that use to be there don't come back, right? And you want to know if its possible to, and/or how to retain the leader notes, even after the component they were attached to goes away, right? And maybe if its possible and/or how to automatically create new leader notes on the new components when you increase the pattern quantity, right?
Wesley Crihfield
(Not an Autodesk Employee)
Unfortunately I don't have a solution for that situation. I'm not even sure if it's possible achieve with leader notes (ModelLeaderNotes). If it were possible it would likely require a ton of code, and some manual set-up. Most types of 3D annotations (ModelAnnotations) require not only annotation planes, but something to attach to. The only one that doesn't require something to attach to is the ModelGeneralNote, but its placement is by screen quadrant, so that wouldn't be accurate enough for this situation. I have done several things with 3D annotations using iLogic, but nothing like this scenario would require. You would likely have to have named entities within one or more of the parts within the assembly, so you have something stable to find and attach to with the GeometryIntent of the leader node. Then to find it you would have to dig down into the pattern to get each occurrence of the assembly, dig into its part, get the named entity, create a geometry proxy of it at the assembly level, then somehow use that proxy as a basis for the geometry intent of the one node in the leader's ObjectCollection when you create each leader note for each occurrence of the assembly. Makes my brain hurt just thinking about the task. 😅 Good luck, if you intend to pursue this automation task.
Wesley Crihfield
(Not an Autodesk Employee)
