You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Generate Unique Value activity that is building a unique OfficePhone attribute. The XPath filter I am using is /Person[OfficePhone = '[//Value]']. Value expression (only one) of "+15555555555;ext="+[//UniquenessKey].
When this runs, it generates error events in the WAL log, with Event ID 41501, such as this:
Exception in 'ExpressionEvaluator : DetermineParameterType'. Details: MicrosoftServices.IdentityManagement.WorkflowActivityLibrary.Exceptions.InvalidExpressionException: The expression 'Person[OfficePhone = '' is invalid..
I'm not really sure what to make of this; I had the workflow succeed once, even though it threw these errors, when I turned on verbose logging, but in subsequent tests I have not seen it succeed; however, the above exception seems like a bug.
Thank you.
The text was updated successfully, but these errors were encountered:
I'm wondering if this has to do with + sign in the phone number which the parser may be misinterpreting as a + operator.. Does this work if you replace + sign in front of the country code with 00?
Hello,
This is for WAL version 2.19.0112.0.
I have a Generate Unique Value activity that is building a unique OfficePhone attribute. The XPath filter I am using is
/Person[OfficePhone = '[//Value]']
. Value expression (only one) of"+15555555555;ext="+[//UniquenessKey]
.When this runs, it generates error events in the WAL log, with Event ID 41501, such as this:
Exception in 'ExpressionEvaluator : DetermineParameterType'. Details: MicrosoftServices.IdentityManagement.WorkflowActivityLibrary.Exceptions.InvalidExpressionException: The expression 'Person[OfficePhone = '' is invalid..
I'm not really sure what to make of this; I had the workflow succeed once, even though it threw these errors, when I turned on verbose logging, but in subsequent tests I have not seen it succeed; however, the above exception seems like a bug.
Thank you.
The text was updated successfully, but these errors were encountered: