Hello,
I am currently creating home pages (lobbies) for different departments.
One department wants to monitor NCR Correction Actions, filtered by severity_id and next_to_act.
Target page for the link: page/NonConformance/CorrectionActionForm
In the page search, both severity_id and next_to_act are available.
next_to_act belongs to the view used by the page projection.
severity_id, however, comes from a selector, so from another data source.
Client-side filtering? Strange, but apparently that's how it works.
As a workaround, I added a read-only severity_id field into the projection view (NCR_CORRECTION_ACTION_CFV).
It is slow and clearly not optimal, but it is the only solution I found for now (I cannot spend 16 hours on this topic, I still have delivery objectives to meet).
As you can see in the screenshot, it works correctly on the DB side.
However, in the Datasource Designer preview, it does not work, despite using the exact same filtering criteria.
The query executed from the page through the linked list works correctly, and returns the expected number of rows.
Looks like a small bug. I do not know whether it has been fixed in newer versions — we are currently running 24R1.
Have a good day,
Guillaume