Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
AlexFielder
in reply to: steveh3

Hi @Owner2229@steveh

 

If I may add my $0.02 on this:

 

I suspect the reason the built-in iLogic save command is failing is because it is interfering with the DocumentEvents.OnSave Event that the Vault addin is intercepting/capturing in order to then display its own file naming dialogue.

 

Have you tried running the rule (for arguments' sake) with the vault addin disabled?

 

I bet your original rule would run just fine in that case.

 

When you run the ThisApplication.CommandManager.StartCommand(CommandIDEnum.kFileSaveCommand) command, (even though you are running it from iLogic) you are overriding the iLogic .save() method using the built-in API command & then Inventor's events fire normally and everything is fine.

 

You could absolutely see this in action if you ran the Event Watcher tool (with the ApplicationEvents.SaveDocument & UserInputEvents.OnActivateCommand checkboxes selected) at the same time as running this rule.

 

Does this error make it a bug? A small one, yes; I don't have knowledge of how many customers are using both iLogic and Vault (paid for) versions with file naming enabled but I am surprised this hasn't raised its head before now.

 

(At my previous company we used Vault Professional with file numbering enabled and although I used iLogic rules to help with mundane tasks I can't recall ever having iLogic save anything in the way your screencast shows. Maybe I found this error and decided the easiest option was to just save manually once the rule completed...)

Tags (2)