Inventor 2025 - Vault iLogic checks issue

Inventor 2025 - Vault iLogic checks issue

jonathan.victor
Advocate Advocate
3,987 Views
19 Replies
Message 1 of 20

Inventor 2025 - Vault iLogic checks issue

jonathan.victor
Advocate
Advocate

I have a simple code on several drawings that run the "Update copied properties" command, this code is set trigger on "Before save" event. In Inventor 2022 the drawing would save & checkin properly, but in Inventor 2025 it's impossible to check-in to Vault if the code is set to trigger before save

 

jonathanvictor_0-1715201864852.png

 

 

Dim oControlDef as ControlDefinition  = ThisApplication.CommandManager.ControlDefinitions.​Item("UpdateCopiedModeliPropertiesCmd")
 
oControlDef.Execute2(True)

 

Is this a bug? Does anyone have the same issue with this "iLogic checks"?

0 Likes
3,988 Views
19 Replies
Replies (19)
Message 2 of 20

bradeneuropeArthur
Mentor
Mentor

Try to use application events not the document events!

Regards,

Arthur Knoors

Autodesk Affiliations & Links:
blue LinkedIn LogoSquare Youtube Logo Isolated on White Background


Autodesk Software:Inventor Professional 2025 | Vault Professional 2024 | Autocad Mechanical 2024
Programming Skills:Vba | Vb.net (Add ins Vault / Inventor, Applications) | I-logic
Programming Examples:
Drawing List!|
Toggle Drawing Sheet!|
Workplane Resize!|
Drawing View Locker!|
Multi Sheet to Mono Sheet!|
Drawing Weld Symbols!|
Drawing View Label Align!|
Open From Balloon!|
Model State Lock!
Posts and Ideas:
My Ideas|
Dimension Component!|
Partlist Export!|
Derive I-properties!|
Vault Prompts Via API!|
Vault Handbook/Manual!|
Drawing Toggle Sheets!|
Vault Defer Update!

! For administrative reasons, please mark a "Solution as solved" when the issue is solved !


 


EESignature

0 Likes
Message 3 of 20

jonathan.victor
Advocate
Advocate

I've tried and had the same results.

Also, now I'm trying to check-in an iAssemblie, that has not a single one rule or even any event trigger set and yet facing the same issue, pretty sure this is a bug on this version. The issue happens when trying to check-in to vault in the factory and each member assembly, rules doesn't exists in any of them.

 

jonathanvictor_1-1715254187108.png

 

 

 

 

 

0 Likes
Message 4 of 20

Curtis_Waguespack
Consultant
Consultant

@MjDeck would you be able to look at this and tell us what the expected behavior is? What we can and can't do using this before check-in trigger, etc?

 

I've run up against this as well, but did not find any information about this aspect of it in the documentation of this new trigger ( maybe I overlooked something?).

 

Thank you!

 

0 Likes
Message 5 of 20

MjDeck
Autodesk
Autodesk

@Curtis_Waguespack , a rule that runs on the new Before Vault Check-In event cannot modify the document. It can only do read-only checks. This is noted in the What's New:
A rule executing on this event must treat the file as read-only. Once saved, the file is prepared for check-in. While the rule can verify values, it cannot modify them.


That is: you save first and then do the check-in. The rules that run during the check-in operation aren't allowed to change the files. If they try, you will get the "Unable to check in files" message.

@jonathan.victor , can you verify that your rules are not set to run on the Before Vault Check-In event? If so, please post sample files or screenshots of the Event Triggers dialog.


Mike Deck
Software Developer
Autodesk, Inc.

Message 6 of 20

jonathan.victor
Advocate
Advocate

@MjDeck The files I've teste on the first moment, and attached the screenshot first time, they had the above code triggered to run on "before save" and it have been working in the last five years without any issue. But in the third reply on this post I've attached a screenshot of a bunch of iAssemblies that don't have rules or trigges configured and show the same behavior (So I think we can forget iLogic issues at the moment), as I'll show below:

 

(While I was recording my screen and writting this message Inventor showed two simillar behaviors, as I will show)

 

#1 Case: I open the file, save document (no errors), press check-in button, Inventor analizes the factory table and proceeds to save model to check-in, trows an save uncessfull error message, close the model and then Inventor crashes itself.

(view in My Videos)

 

#2 Case: I open the file, save document (no errors), press close document, Inventor asks if I wanna check-in to Vault, confirm check-in, Inventor proceeds to analyze factory members, all looks fine, check-in dialog show up and then I confirm check-In to Vault, then Vault trows the "Unable to check in files" error with "The file was modified by a rule that ran on check-in." restriction for each member, wich not a songle member or subcomponent has any rule or trigger defined. I showed the event triggers dialog and it doesn't have rules to be run.

 

(view in My Videos)

 

 

jonathanvictor_0-1715272921844.png

 

Those files haven't any change or revision from last version (2022), i just opened them and went to check-in in newer version (2025).

0 Likes
Message 7 of 20

MjDeck
Autodesk
Autodesk

@jonathan.victor , can you post one of the files that can't be checked in?


Mike Deck
Software Developer
Autodesk, Inc.

0 Likes
Message 8 of 20

jonathan.victor
Advocate
Advocate

See attached files.

0 Likes
Message 9 of 20

jonathan.victor
Advocate
Advocate

Sorry, I replyied myself by mistake.

0 Likes
Message 10 of 20

MjDeck
Autodesk
Autodesk

Hi Jonathan - Thanks. I tested with your assembly and I was able to check it in with no problem.

Can you check for extra copies of a file named RulesOnEvents.xml on your system? That stores the event triggers for all documents. Please check to see if you have a file with that name in your workspace. If you do, please move it somewhere else. 
If that file does not exist in your workspace, please send me a copy of the file from your External Rule Directory folder (as set in the iLogic Configuration dialog). Since you have no event triggers set, that file should be almost empty. It should have no rule names.

If you haven't already done so, please try exiting and restarting Inventor.


Mike Deck
Software Developer
Autodesk, Inc.

0 Likes
Message 11 of 20

jonathan.victor
Advocate
Advocate

Hi @MjDeck I've searched and I found one copy of that file on my PC, changed it's name and tested again, the same error showed up. I also changed the on in external rules directory and got the results. Right now I have tested check-in on another computer, one of my colleagues with the same settings as mine, and got the same errors including the Inventor crash behavior. I have attached the external file below. And as I see, no rules are defined there.

 

jonathanvictor_0-1715280106803.png

 

 

0 Likes
Message 12 of 20

MjDeck
Autodesk
Autodesk

Hi Jonathan - you only have one External Rules Directory, is that correct? (It's possible to add more than one.)

As a test, can you try removing that directory in the iLogic Configuration dialog? Then restart Inventor.
There is no need to delete it in Windows. Just remove the name in the iLogic Configuration.

Do you have any 3rd-party add-ins loaded?


Mike Deck
Software Developer
Autodesk, Inc.

0 Likes
Message 13 of 20

jonathan.victor
Advocate
Advocate
Yeah, we only use one directory, and none of the rules there is configured
to have an trigger event.
0 Likes
Message 14 of 20

MjDeck
Autodesk
Autodesk

Hi Jonathan - we have been able to reproduce the problem. As a workaround, please disable rules on events before checking in, and re-enable them after checking in. You can disable them in the dialog shown by the Options button on the Event Triggers dialog, as shown in the screenshot in your Message 6 above.


Mike Deck
Software Developer
Autodesk, Inc.

Message 15 of 20

jonathan.victor
Advocate
Advocate

Hi MjDeck, I've teste your hint and it worked! Disabling and then checkin files made the errors disapear also, after checkin in the files I turned it on again. It's is a workaround that helps, but autodesk needs to solve this problem, since this is an annormal behavior from Inventor. We have several documents that uses event triggers and its not right to turn then on/off everytime.

 

jonathanvictor_0-1715286664534.png

 

jonathanvictor_1-1715286687809.png

 

 

Message 16 of 20

MjDeck
Autodesk
Autodesk

Yes, I think we can fix it soon. Thanks for reporting it. This is internal issue INVGEN-77745.


Mike Deck
Software Developer
Autodesk, Inc.

Message 17 of 20

MjDeck
Autodesk
Autodesk

@jonathan.victor , we have been able to reproduce a problem with the iLogic Checks dialog blocking the check-in operation. But so far, we haven't been able to do it with the assembly you sent us. Do you have an old copy of the assembly as saved from Inventor 2022? If so, could you post it?


Mike Deck
Software Developer
Autodesk, Inc.

Message 18 of 20

jonathan.victor
Advocate
Advocate

Hi @MjDeck , sorry for late response, unfortunatelly, we have only the migrated version of that iAssemblie, we could download the older versions from vault, but since that iAssemblie Ihave uploaded before has several another iParts inside, I don't think it would have only the older versions of each iPart. Another thing I noticied, is that the "All events enabled except 'Afeter Open' and 'Close' Recommended setting" option has worked just as fine as the "None" option. If you want to got an 2022 version of the "vedação.iam", I can try to get the older version, but I can't guarantee it will have only the older versions. Thanks ever since, plase keep us update for this issue topic for furter solutions and future fix on next updates.

 

jonathanvictor_0-1715773750502.png

 

0 Likes
Message 19 of 20

MjDeck
Autodesk
Autodesk

Hi Jonathan - thanks. If you have any other iAssembly models like this, but you have not opened them in Inventor 2025 yet, please keep a backup copy of the 2022 version.


Mike Deck
Software Developer
Autodesk, Inc.

0 Likes
Message 20 of 20

sergicasadogarcia
Contributor
Contributor

🤘Hi everyone,

 

With this post, I was able to solve my issue with iLogic and Vault by using external rules. I don't know if this post will help you, but I tried changing the trigger to "before saving the document," and it solved the problem. In my case, Vault and the "after save the document" trigger were causing issues.

 

Regards.

Sergi Casado.

Please mark a "Solution as solved" when the issue is solved ! And a Like if it helps you.
0 Likes