Vault Revision Block not updating correctly

[christian_skare]

Hi,

I'm having some hard time to understand how the Vault Revision table works in Inventor.

When Vault triggers the PDF generation, the revision table is missing the 'Approved' fields.

In Inventor I've changed the Vault Revision table layout to how I want it, and then changed the Vault mapping to those column headers.

This is my work in progress file, no data in either Checked By, Approved By or Approved Date.

Fast forward, I've checked and approved the drawing. Data has been entered.

During my transition For Approval → Approved, I've synchronized Properties and created a PDF.

PDF has the same data filled out as my idw, so synchronize properties works.

Job Queue has no issue running Sync Prop, Update revision block nor create PDF.

Everything looks good in Vault. Lets check PDF.

Approved field is missing the data from Vault, but the other was populated correctly.

PDF is created from the idw, so IDW is the same.

If I populate with vault data, my column is populated correctly.

Since "Populate with vault data" populates my data, all vault properties are mapped correctly to my revision table - correct?

Why is 'Approved' missing unless I manually click this button?

Unsure if this a Inventor related post or a Vault forum post, so mods can move it if necessary.

Thanks in advance! 🙂

[CGBenner · Accepted solution]

@christian_skare 

Hi, Take a look a this class that the late great Mark Lancaster and I did at Autodesk University in 2019 where we went through setting this up in Inventor and AutoCAD, and even threw in the use of Change Orders just to make things interesting.  Pressing enter at the end of the demonstration and seeing the revision update as expected was one of the highlights of the conference that year!  LOL

Good luck!

[christian_skare]

Thank you very much, Chris.

I skipped to the demo first to check out what you're actually doing here, and I believe one very important point answered my forum post.

Around the 57th minute:
"Very important point!
The vault revision table update will only work on a file that has already been on a released state once.
If this is your initial release, you're gonna do the revision manually, check it in to the vault, set it to released, then the vault revision table take over at that point.
So if it hasn't been set to released and you go through all of this, then you're gonna be really let down when nothing happens."

Which is what I'm experiencing. If I go through the release state again, it will populate my revision table, but not the initial release.

Do you know of a workaround here? Or am I wasting time trying to get this to work?

Our lifecycle state is set up like this:

Thinking out loud now, and my first thought is to bring in a new released state.

Just because a document is or has been in a released state, doesn't require me to bump the revision before the next released state?