xref components erroneously showing out of date when nested

[bold.stelvis]

I'm having an inconsistent but unfortunately frequent issue

if I bring in a referenced component and then nest that within another 'parent' component in my working file it will often (but not always) suddenly show out of date even though its not and no amount of updating to latest will fix it.

I'm nesting it in order for me to be able to quickly show/hide various sub assemblies as I work -  ie primarily for convenience - is doing this somehow not a good strategy?

does seem to be a bug anyway

[innovatenate]

Thank you for posting about this issue. Can you share the fusion design with us?

Thanks,

[bold.stelvis]

sure  I'll pm you with details

thanks for looking into this - I can't seem to find a consistent method to why it does or doesn't happen, but I am getting it very frequently

[innovatenate]

Thanks for sharing those with me. I've logged a report with development for this issue (reference ID FUS-28417). 

The out of date warning message seems to be falsely triggered after moving those components to another component group in the browser. 

I have found that if I first activate the component group called "fasteners," I can insert the components without any issue. I'm not sure why moving them in the browser would cause this. I'll circle back here with what I learn from the report.

Thank you for reporting this!

Best,

[bold.stelvis]

ok, great - thanks for the tip on activating first 🙂

[keqingsong]

Good news! This issue will be fixed in our next update in December!