Power Apps - Prefilter Functionality

What does this functionality do?

The pre-filter feature is designed for clients managing substantial data in their Dataverse who seek to selectively import a limited amount of data to OnePlan. 

The functionality relies on user-created filters accessible in the Filters page. These pre-filters are only applicable to the Power Apps Entities -> Plans level. The pre-filter functionality only influences the transfer of data from Power Apps to OnePlan.

The Pre-filter functionality applies to two strategies in the Power Apps integration: DynamicsEntity_to_OnePlanPlans and DynamicsEntity_to_OnePlanResources.

For more information on filter anatomy and potential use cases, please feel free to review Understanding Strategy Filters.

Enabling Pre-Filter 

To enable pre-filtering, two things need to occur:

1. The Use Pre-Filter for filtering checkbox must be checked. 
2. Filters must be applied to either the Epics - Plans table or the Issues - Backlogs table within the Mappings > Filters section.

Applying the Filters

Filters are broken down into four segments: Select Field, Select Operator, Value Field, and Logical Connector.

Select Fields are all fields mapped within the Mappings > Fields tables. Please note that the field mapping must match the table that the filter is being applied to.

Select Operators enable you to define the type of comparison (or operation) to be performed on the Select Field. The set operators allow you to precisely specify how the field value should relate to the condition you are establishing. This selection determines the criteria for including or excluding data based on the chosen field, enhancing the flexibility and precision of your filters. 

Value Fields are where you input a specific value against the chosen field and will be compared during the filter process. Depending on the operator selected in the Select Operator field, this value defines the condition that the data in the chosen field must meet to be included in the result set. 

Logical Connector serves as the bridge for constructing sophisticated queries or filters by connecting multiple conditions. When you have more than one query condition, the logical connector lets you specify how these conditions should interact. You can choose between 'AND' and 'OR' to dictate whether all conditions must be met, or if at least one of the conditions should be satisfied.  To extend the current filter to apply the Logical Connector, click Add Filter. 

Once a suitable filter has been created, click Save.  

Note: The field being filtered on must be available for all entities/plan types. 

Filtering and Comparing Date Fields

When directly comparing with a date field (e.g., Due Date = 12-31-2000), setting up the filter remains straightforward. However, when dealing with comparisons like Due Date >= 12-31-2000, the filter may not function as intended. This is because the dates are treated as string values in this scenario. For proper date field comparisons, please ensure the date value is enclosed within number signs (e.g., Due Date >= #12-31-2000#).

Filtering on Boolean Fields

When filtering on Boolean fields (e.g., Is Active = true), the Select Operator must be set to IN. This is because Power Apps processes Boolean values using the IN operator by default. Since OneConnect does not automatically identify Boolean fields, using this approach ensures the filter functions correctly and aligns with Power Apps' expected behavior. 

Filtering on Choice Fields

If filtering on a choice field, from the Select Field dropdown list, select the Choice Field Name (ID) Plan Type (e.g., Business Unit (ID) Project). The Value Field to be filtered on will be the GUID ID.

Locating GUIDs for Choice Fields

If filtering on a choice field, from the Select Field dropdown list, select the Choice Field Name (ID) Plan Type (e.g., Business Unit (ID) Project). The Value Field to be filtered on will be the GUID ID.

Locating GUIDs for Choice Fields in OnePlan

1. Open the OnePlan Configuration page by clicking on the Settings (gear) icon.
2. Go to Fields, expand Plan Fields.
3. Locate the choice field desired and click on the Edit icon. The Edit Choice form will open.
4. In the column title, click on the dropdown arrow to expand the options available, select Columns, and select Id. These values are the GUIDs for the specific choice option.

Pre-Filter Best Practices

Test Filters one at a Time

It is recommended to apply filters based on a single value at a time. Utilizing multiple filters might introduce unintended complexities, potentially resulting in the inclusion or exclusion of unexpected data during the transfer process. Keeping the filtering focused on a single value enhances precision and reduces the risk of unintended data being brought into OnePlan.