The ordering of the child records within the parent editor requires a sort field to be defined. If re-ordering is disabled, this can be represented by two values: with errors, with no errors, with the actual values being such that the one for errors appears in the list first. Then a Change Notification rule could set this "sort" flag based on whether there was and error or not. The down side of this approach is that the records cannot be sorted any other way (within the error list and non-error list). An advantage is that the update is near-instantaneous.
Another approach is to launch a combo export -> import that extracts the updates needed to re-sequence the records according to the rules. The advantage of this approach is that the entire set of records can be sorted on more than just the has error/does not have error. The down side is there would be data latency between the changes and when the sort is updated.
-Brian
There are also cases where the validation state of a record may change due to change dependent changes in other objects (records, code sets, etc.) could result in some records currently flagged with errors to becoming valid, but that would require the validation job to run.
Another option is to configure the link relationship so the selected to allow the list of children to appear on a separate tab with a user preference selected. That user preference could have a pre-defined sort already in place that places the error at top. This approach also supports doing other operations on the list of records (search, sort, purge.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------
Original Message:
Sent: 05-13-2021 07:09
From: Jeff Wiedemann
Subject: In Linked Relationship, Sorting Child Records by HAS_ERROR_IND
I have a scenario where by 100's of SKUs can be attached to a single product. While displaying the linked SKU records from a Product, the user would like to see those with validation errors sort to the top. This can all be done using Change Notification but then the issue exists where a sort field will need to be maintained.
I was wondering if there was a better way to use B_MASTER_REPOSITORY_ITEM which is maintained by the system and reflects the state of the item since last validation ... opposed to maintaining a sort field on SKU.
------------------------------
Jeff Wiedemann | Engineer, Apps
Steelcase, Inc | 616-460-0597
------------------------------