Hello Experts,
I am reaching out to inquire if any of you have experience utilizing BDE filters to exclude content by employing the extended LN fields within the UserArea, as demonstrated in the following code excerpt. While the filter operates seamlessly with standard fields, it appears to encounter an issue when applied to extended fields, resulting in an error. Any insights on this matter would be greatly appreciated.
Operational instance utilizing standard fields.
<ComparisonExpression>
<comparisonOperator>gt</comparisonOperator>
<attributeName>ServiceOrder_v4.serviceOrderCode</attributeName>
<instanceValue>HT0000001</instanceValue>
</ComparisonExpression>
Here is an illustration utilizing extended fields that I am attempting to operationalize.
<ComparisonExpression>
<comparisonOperator>eq</comparisonOperator>
<attributeName>ServiceOrder_v4.UserArea.Property.NameValue[
@name='OrderDuration']</attributeName>
<instanceValue>1</instanceValue>
</ComparisonExpression>
Error thrown:
<faultstring>No valid filterAttributes received. (filterAttribute received "ServiceOrder_v4.UserArea.Property.NameValue[
@name='OrderDuration']")</faultstring>