DNM attribute and updating libraries

[erik.buerV95QJ]

We use a No Not Mount (DNM) attribute to manage components to be placed and not. 
Every time we update components from the database, we get consistency errors like the picture below.
Going over these is time-consuming and should be unnecessary. It didn't use to act this way in the earlier versions of Fusion (?).

We have a separate PDM system that grabs the DNM attribute from the BOM CSV.

There should be some more appropriate way of managing DNM-components, which is visible from the schematic view.

There is the populate bool in the PCB editor, but this bool is, as far as I can tell, not visible in the schematic view.

Below we can see the way DNM is shown when using an attribute.

This is clearly visible in the exported drawings.

It is unfortunately visible on our assembly drawings.

Can we go back to the old way of not overwriting the attribute in the PCB only, when updating components from libraries?
Also, a proper way to manage non-populated parts would be appreciated. 

-Erik

[jorge_garcia]

Hello @erik.buerV95QJ ,

I hope you're doing well. This is unusual, do you have the board open when you do this update? You've been on these forums for a while so I know you know the importance of consistency, but I wanted to confirm just in case.

The Variants functionality (available in the Document menu) is the currently recommended way to handle components that are not populated. You can switch between different configurations of components being populated or not. 

If for this design you need to fix the attributes, it's possible to correct them using the copy-attrib-sch-to-brd.ulp that comes with Fusion 360 and that will copy the attributes from the schematic to the board. That should get you out of trouble right now.

Best Regards,

[erik.buerV95QJ]

Yes, we have all the files open.
The "Variants" feature shows promise. It seems that the variant component status is not visible on the schematic?

I'll check out the copy attr. script.
Thanks! 

[erik.buerV95QJ]

Hmm.

So when I try to run the attribute ULP you mentioned, I get the following errors:

Restarting fusion and running the ULP again, i get the following error message:

After clicking "OK", it seems that the consistency error has been solved (?).

[jorge_garcia]

Hi @erik.buerV95QJ ,

I hope you're doing well. That is unusual, it might have something to do with how the undo stack is treated when a ULP runs. Would you be willing to share a version of the files where the inconsistency is present and then we could try to recreate the message. That will help us diagnose what's going on.

I'll send you a DM with my email address.

Best Regards,

[jorge_garcia]

Hi @erik.buerV95QJ ,

When you want to change the DNM attribute, how do you do this? Are you changing it in the library and then trying to do an update to the schematic/board file. Are you creating the attribute straight on the schematic.

I'm trying to get clarity on how this attribute is created in your design.

Best Regards,

[erik.buerV95QJ]

We have the "DNM" attribute defined but with an empty value field in the library.

Then we assign a "DNM" value to parts in the schematic.