Trying to change state to released, getting error

[Anonymous]

While trying to release an assembly drawing, I am getting an error that I cannot change the specified state due to an error.  The error is that the assembly is not released.  Why can't I release a file that is not released?

[bastian.estner]

Hello Ronald,

It seems you try to release an Inventor drawing that has a non-released assembly on it from your screenshot. 

I assume that the lifecycle your drawing is in requires child files to have the released state when you try to transfer it, and that the mentioned assembly is not in such state.

Could you verify if the following setting is similar in your environment for your lifecycle transition?

 

Best regards,

Bastian

[Anonymous]

@bastian.estner  thanks for the reply.  You are correct, the check box is selected.

[Anonymous]

@bastian.estner  I guess I need to provide more information, that did not solve my issue.

The issue is with this file.  I have many other drawing files with assemblies that are not released that I can change the state of the drawing file to released without issue.

One thing I just noticed is that the new lifecycle state drop down menu is null for this drawing, but not others.  That might be more of the issue I am having.

[bastian.estner]

Hello Ronald,

I understand being surprised when you have a lot of drawings that work in the way you've described but one behaves different.

Could you please compare "Category Name" and "Lifecycle Definition" and "State" from the System Properties for this file and a file that works as you described? Are they identical? Is it exactly the same transition you're trying to do here?

Additionally, I'd like to make you aware that the check for "Released State" is not meaning that Vault checks if the child files are in a state that is called "Released" but in a state that has the 'This is a "Released" state' flag enabled.

This information could be different for the "working" files if they are in another state and lifecycle.

Best Regards,

Bastian

[Anonymous]

@bastian.estner  I checked and the top level assembly and the "Category Name" and "Lifecycle Definition" and "State" all match other files.

However, at one point, I had a STEP file in the assembly, and the fields for those files are blank.  I think I need to add that file type.  What gets me, is that the STEP is no longer part of the assembly.  I am just not sure what else it could be.

[bastian.estner]

Hello Ronald,

Could you send me a picture similar to the one below from the drawing where you get the error message that has the same columns (you can insert columns by right-clicking on the column header and selecting "Customize View...") and all nodes expanded?

I assume that some of the childs could miss the "Released Revision" Flag.

Best regards,

Bastian

[Anonymous]

See below.  I cannot send the entire assembly, it has dozens and dozens of part.  What is the point of that flag?

[bastian.estner]

Hello Ronald,

The point of this flag is that it indicates if the file is in a "Released State". 

In other words, when you try to release the top assembly, Vault checks if this flag is active for all subassemblies and parts.

In your screenshot, this is not the case.

Therefore, the transition criteria mentioned earlier to check if child files are released will result in the error you described initially.

If you want this criteria to stay active, ensure that all components are in states that have the "This is a Released state" active.

Practically, you could use the view you've created to identify all components (subassemblies and parts) that are not meeting this criteria and move them in such state.

Afterwards, you should be able to release the top assembly and its drawing.

Best regards,

Bastian

[Anonymous]

Is the point of the flag in the control tab of the lifecycle definition page to allow someone to name a state that acts like a "released" state something else?  You could have a state called "complete" but in order for the vault to treat it as a released state, you would have to have this box checked.

As for my issue, it sounds like for this top level file, a drawing, I cannot release it until all the dependents are already released.

What I do not understand is how I got here.  I have changed the state of hundreds of top level files to a released state without ever having to released the dependents first.

Any idea how something like that happens?  What could be different about this top level than all my other top level files?

[bastian.estner]

Hello Ronald,

The scenario you are describing is one reason for this flag yes. There are others that can be found in the product help here: http://help.autodesk.com/view/VAULT/2021/ENU/?guid=GUID-02294D64-9ACA-4546-956E-095D9D7814B1

Your conclusion regarding your issue is exactly what I would expect as well with one addition: You could release the top drawing and assembly together with all non-released files in one process as well.

Speaking of all the files you have sucessfully "released" in the past, the following things could have changed meanwhile:

1. The transition criteria settings could have been changed. maybe they have been set to not check for released child files.
2. The files you've released in the past may have been assigned to other categories and lifecycles with other settings for transitions and state security.
3. The revision of your files have not been bumped in the past when going from a released state to for example work in progress. 

All these possible causes would have required somebody to change administrative Vault settings in your environment and all of them are not logged.

Best regards,

Bastian

[Anonymous]

@bastian.estner  thank you for the feedback.

However, I am really confused now.

I concluded that I would have to start at the lowest levels and release files from the bottom up.  You stated I "...could release the top drawing and assembly together with all non-released files in one process as well."  That is not the case.  That is what I am trying to do and I am getting errors.   If I could do the latter, I would not do the former.

I am the only administrator to the our vault, unless someone has unauthorized access and I did not make any of those changes.

[bastian.estner]

Hi Ronald,

You could set up your state change to include all components and select a released state for all drawings. This would transfer all of them to the states you've selected.

Its just that you do not have to do this prior but you could do it at the same moment as well.

I've created a quick vidoe to clarify what I was referring to:

https://autode.sk/3cKWNhp

I hope this solves the confusion.

Regards,

Bastian

[Anonymous]

@bastian.estner 

Thanks again for your suggestions.  I just wished they worked.

I have a new drawing with new parts that is giving me the same error.  I have a couple sceencasts, but I am not sure how to attach more than one at a time.

[Anonymous]

and the 2nd

 

[Anonymous]

Now I am getting errors trying to post the screencast.  I am out of ideas.

[bastian.estner]

Hello Ronald,

The solution seems to be close here.

What I can see from the first Screencast you've posted at least is that you click the option button to include dependent files at 7 second mark. 

When you click it again at 8 seconds, it resets to "Work in Progress" for all components.

Does it run into an error when you try to release it with all components selected for "Released" state as well?

Regards,

Bastian

[Anonymous]

Hello again.

Good catch.  I switched it back to released and got the same error.  I thought that was it for a minute, but i am still out of luck.

[bastian.estner]

Hello Ronald,

please PM me with your phone number and I will try to call you.

I think I could see a lot more when looking on your environment directly.

Best regards,

Bastian