2022.2 Make Components : Selection Dialog not working

[DavidKuhlmann]

When using the Make Components : Selection dialog in 2022.2 the "Next>>" button is grayed out when attempting to place another solid into an existing target assembly.  This process has worked until Inventor 2022.2.  Is there another process to replace this functionality?  A work around is to uncheck “Insert components in target assembly” but then the individual parts have to be placed into the target assembly manually.

This doesn’t seem to be a problem if the target assembly does not already exist.

Thank you

[Gabriel_Watson]

You are missing a template used to create the new component:

This is also set under the Document Options:

[DavidKuhlmann]

When I adjust the Target Assembly Name to match the existing assembly file name in the Make Components : Selection dialog the Template dropdown grays out.  The Template dropdown is only available in the Make Components : Selection dialog when the Target Assembly does not already exist.  This has worked until the 2022.2 update was installed.

Thank you

[Gabriel_Watson]

I see. I have the same issue here. I can only pick "Yes" and replace an existing assembly, not add to existing.

[SharkDesign]

You don't need a template is you're putting it in the current assembly because an assembly already exists.

[SharkDesign]

I've just tried 2022.2 and get the same issue. 

It asks you to select a target assembly, but when you do it it goes grey. 

They've updated this tool in 2022.2 to accept invisible parts and surfaces so they may have broken something else. 

[DavidKuhlmann]

It worked until 2022.2.

Thank you

[johnsonshiue]

Hi Folks,

This is indeed a bug in 2022.2. It should work. At least it used to work in 2022.1 or earlier. Pushing solid bodies to parts in an existing assembly is a legitimate workflow. I am working with the project team to understand it better. Hopefully, we can resolve it soon. In the meantime, if the issue blocks your workflow, please uninstall 2022.2 update for now. I am very sorry!

Many thanks!

[LauriLink]

i and many other engineers have same problem after installing 2022.v2

When fix will be available?

[johnsonshiue]

Hi! This is indeed a regression from 2022.1. It has been reported as INVGEN-57952. We don't have a fix yet. In the meantime, please uninstall 2022.2 update if the behavior blocks your workflow. Hopefully, we will address it soon.

Many thanks!

[JamesSlaven8282]

Hello,

I experience the same behavior.

Looking forward to the fix.

James

[BDCollett]

---

@johnsonshiue wrote:

Hi! This is indeed a regression from 2022.1. It has been reported as INVGEN-57952. We don't have a fix yet. In the meantime, please uninstall 2022.2 update if the behavior blocks your workflow. Hopefully, we will address it soon.

Many thanks!

---

The 2022.2 update already fixed a lot of problems that 2022 introduced.. this is rather frustrating.

At least you can still create component and save it and then add to an existing assembly as a workaround. Glad this was brought to our attention.

[David_G_Rodriguez]

This is a somewhat major problem right? Will this be fixed anytime soon? I uninstalled the update, but then we have the problem of it showing us files are out of workspace when trying to check-in even though they are.

[johnsonshiue]

Hi Folks,

I am sorry that 2022.2 update breaks this workflow. We are actively working on a fix. We have identified the offending change, which was meant to address instability in a workflow. But, there was a logical flaw leading to blockage in Make Components dialog. In the meantime, please uninstall 2022.2 update.

Many thanks!

[Sim-event]

Hi All,

Hoping somebody can point me in the right direction?

I am aware of this flaw with the 2022.2 update (INVGEN-57979) as i have commented on another thread.

I now have two problems! Problem one, everyone from autodesk keeps commenting to roll back, but all versions of earlier installer seem to be unavailable or am i missing something? Is there functionality within inventor to roll back? I went from fresh install so my only options appear to be 2022.0 or i use the update patch to take it to 2022.2

Secondly, presumably related to the first problem. When splitting a solid in my multi body part, the resulting body in the assembly now becomes a sub assembly. The previous behavior  would update the assembly to only show what it considered to be left of the original part, you would then promote the remaining part or parts using the make component tool( which is the operation currently broken). has anyone else seen this acknowledged as a problem?

I work solely with multi body parts and the plugin woodwork for inventor, at the moment this has decimated my workflow and is costing hours a day to workaround. any input gladly welcome

regards

Simon

[SharkDesign]

Go to control panel

Add remove

View installed updates

[Sim-event]

Thanks James, 

Unfortunately i need to roll back to the last stable release of 2022.1.1, as this is a fresh install i only have the install option of returning to initial install which is far to flawed to be of use

Kind Regards

Simon

[Jeffrey_Jordan]

We are having the same issue with Make Components not working with an Existing Target Assembly.  This is a major workflow issue.  Posting to reinforce the urgency for this fix!

Also, I've found over the years that the more uninstall/reinstalls are performed, the less stable Inventor becomes.  Your fix scares me.

[Jeffrey_Jordan]

Digging and now 2022.1.1 is no longer listed in your updates section.  Where is it and why did you remove it from the updates page yet keep 2022.2 still there?

[Jeffrey_Jordan]

@johnsonshiue I was able to uninstall 2022.2 per your recommendation.  I tried to install 2022.1.1 from the install file I had previously downloaded (since it's no longer listed on your updates page).  Now I can't create an assembly at all without Inventor crashing due to the issue you already know about: https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/When-...

What is the correct course of action?  The reason we updated to 2022.1.1 and 2022.2 in the past is because 2022 had some serious functionality issues.  Now that we have 2022 files we can't go back to 2021!  You've left us stranded.