Value Class - Filter

• What is the Value Class Filter option?
• How do I use mapping filters in different repository types?

Tip

Summary: The Value Class - Filter option in the Mapping Filter table allows for an autonomous definition of the filter. This option works the same as the Constant option, but the Filter Value completely replaces the filter routine. Examples of how to use mapping filters in different repository types are provided, such as Table/Record Pool, XML Node, JSON Token, and SharePoint List.

The Filter option is only possible as a Value Class in the Mapping Filter table. This option works the same as the Constant option, with the difference in the use of the filter. The Filter Value completely replaces the filter routine and therefore enables an autonomous definition of the filter.

How to use mapping filters in different repository types

Mapping filters are technically carried out in the source code.

Table / Record Pool

<Field>.SetFilter(<Value>)
(for example, Value = '01.01.2017..31.07.2017')

XML Node

XPath += <Value>
(for example, Value = '/book[price>35.00]')

For a filter value, the language code of the processing user must be considered for Microsoft Dynamics 365 Business Central fields.

JSON Token

Temp.Field = <Property>
Temp.SetFilter(<Value>)
not Temp.IsEmpty

SharePoint List

<Query><And><Value></And></Query>
(for example, Value = '<Eq><FieldRef Name="MyIntField" /><Value Type="Text">1234</Value></Eq>')

Feedback

Submit feedback for this page .