AnsweredAssumed Answered

Is this a current bug, or is it a previous bug that has been fixed..?

Question asked by Alex Lachance on Apr 9, 2019
Latest reply on Apr 10, 2019 by Josh Brady

We use promoted assemblies in our trailers a lot to be able to control certain things with patterns and what-not.

 

One of the things we drive with patterns and promoted assemblies are the bunks and the installation of winches and pockets on the bunks.

 

So, there's a promoted assembly for the installation of the bunks. The bunks are driven by a pattern sketch since the positions vary in length and height on the trailer. This is the promoted assembly, as you can see, each configuration represents a different assembly with the configuration named accordingly

 

 

There's also a promoted assembly for the installation of the winches and the pockets. It uses the same sketch driven pattern as the bunks do. This is the promoted assembly of the winches and as you can see there's a bunch of configurations named accordingly to whatever it represents in term of position. We will refer to this as Promote1

 

 

 

 

The reason we rename the configurations is because we use the name of the configuration as an annotation to reference what position it is. This is what it looks like on the drawing:

 

We will refer to $PRPMODEL:"SW-Nom de la configuration(Configuration name)" with ''Annotation1'' for now.

 

 

 

The number in the annotation references the position of the winch.

 

 

 

We implemented this in 2014. When we were in 2014, in order to get Annotation1 to show the promoted assembly's configuration name, we were required to select the promoted assembly's origin.

 

When we moved to 2016, everyone was happy because we were able to get the promoted assembly's configuration name by selecting any component from Promote1. That facilitated the insertion of Annotation1.

 

We moved about a month ago to SolidWorks 2019 SP2.0. It seems everything has gone back to how it was in 2014. So what I'm wondering is, what is the intended functionality here?

Is Annotation1 supposed to pick-up the top-level assembly of that said component no matter if it is promoted or not?

OR

Is Annotation1 supposed to pick up the component you are selecting's configuration.

 

Just to be clear, the problem I have right now is that Annotation1 reflects the assembly's configuration name inside Promote1 instead of reflecting the configuration named of Promote1. Notice the configuration name on each assembly on the screenshot of Promote1

This is what we want(2016):

This is what we have(2019):

Outcomes