If Origam.Rule logging is enabled on level debug and there is a data structure rule related to an entity with an array field with a default lookup, rule evaluation fails.
Initial research points to lookup evaluation for the array field, where the numeric value is supplied instead of guid.
I see a test for an XmlDocument. This seems old. But maybe unrelated.
I would also think about ending gracefully (catching and logging any error) inside the logging procedure.
At the moment the error is logged and the exception is suppressed, so the user doesn’t see anything in the UI, but the rule just doesn’t work.
An example has to be prepared.
The example is ready.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.