When using a query and applying filters to classification or business object type fields, there are instances in which the data may not filter as expected. This can happen when the referenced classification or business object records are renamed, and the query is filtering on those name values. To summarize the scenario:
- (1) A user creates a record that contains a classification field, and populates that classification field with a value.
- (2) Another user changes the name of the classification record, which was used to populate the field in #1.
- (3) A user then runs a query that contains the field referenced in #1, and tries to filter values…
In order for filters to take effect for the most current value of a classification or business object type record when changed, records referencing those values in their fields must be updated. One approach to doing this is writing a simple workflow that updates the referenced data:
- Start Task: Workflow triggers on the classification object.
- Task 1: Gets the associated referenced object.
- Task 2: Clears the classification value.
- Task 3: Maps the classification field as the “Source” to the target field.
Note: For every object that the classification field references, the 3 tasks must be repeated. The workflow should only be triggered as an asynchronous process, since the workflow processing time will vary with how many records need to be updated.
[Admin: This post is related to the 06.08.17 post about SQL data not matching the viewed application data, and the 01.04.17 post about filters failing when using changed classification values. To see other related posts, use the Filter tag.]