iLogicVb.Automation.DeleteAllRulesInDocument(oDoc) Causing Catastrophic Failure Error In Inventor 2025

[mjuengel]

I have an iLogic rule that ran fine when using Inventor 2023, but after updating to 2025, it produces a catastrophic error.  I have narrowed down the offending line of code to the following:

iLogicVb.Automation.DeleteAllRulesInDocument(oDoc)

The error does not occur until the rule finishes and everything appears to be working, so I am confused why there is an error message.

[MjDeck]

Hi @mjuengel - can you provide more details, and maybe a test model? If you can't share them on the forum, please send me a private message.

[mjuengel]

I really can't share the exact code as this is part of a confidential project.  The code is at the end of the rule and appears to run correctly.  The SaveAs works with the file closing the file with the rules deleted, but the error box appears right after the document is opened (ThisApplication.Documents.Open(oPathName)).  If I remove the "iLogicVb.Automation.DeleteAllRulesInDocument(oDoc)", then there is no error, but the rules are not deleted.

        Dim fPathName As String
	Dim oDoc As Document
	Dim iLogicAuto As Object
	Auto = iLogicVb.Automation
	iLogicAuto = Auto
	iLogicVb.Automation.DeleteAllRulesInDocument(oDoc)
	oDoc.SaveAs(fPathName, False) 'True = Save As Copy & False = Save As
	ThisDoc.Document.Close(True)
	On Error Resume Next
	ThisApplication.Documents.Open(oPathName)
	On Error GoTo 0

[MjDeck]

Thanks for reporting this. I can see the problem. It is a bug in iLogic. I created internal issue INVGEN-85927.

You could work around it by running that rule as an external rule, instead of storing it in the document. Would that be compatible with your workflow?

[mjuengel]

I will work on that approach.

Thank you

[mjuengel]

I did try implementing the code in an external rule, and I get the same error message.  Can you confirm it does the same for you?

[MjDeck]

I haven't tried, but I expect I would get the same error.
My idea was to implement it in an external rule and also: do not call that external rule from a rule in the document. Instead, change your workflow so that the whole operation is done from an external rule.

[mjuengel]

What do you mean by "change your workflow"?

[MjDeck]

When I say workflow, I mean the steps you take to run that internal rule that deletes the rules and does the SaveAs.
What are the steps you take to run it? Do you run it manually from the iLogic browser?

[mjuengel]

I can run it by manually running an internal rule to set the file name, and then manually running the external rule to change the model and do a save as.  No error message this way.  Do you have any idea when I can expect the issue to be corrected, so I won't have to manually run 2 rules?

[MjDeck]

What is in the internal rule? Maybe it can be added to the external rule instead.

[mjuengel]

It could, but there will be multiple models that use the code.  This will result in multiple external rules, one for each of the different models.  Please let me know when Autodesk fixes the issue.  Thank you

[MjDeck]

We might be able to release a fix on September 9. If not, it would be in December.

Are you sure you can't do everything in a single external rule? An external rule can read parameters, iProperties, and the filename from any document that you run it on.

[mjuengel]

I could, but then I would have to have multiple external rules for each model type that would use it.  We will manually run 2 rules and wait for the fix.

Thank you