PLP Register Fields filtering on only one page after upgrade to 8.2

[photon]

We have thousands of IDs in our PLP register. Let's say ten of them are named Aaron. I can sort the register on the FirstName to see all of the Aarons on the first page. If I apply a filter to the column to only show people named Aaron, all ten of the Aarons display. However, if I sort the register by last name, for example, and filter on Aaron in the FirstName column, zero show up. If move to a page that has, say, one or two of the Aarons, then filtering on Aaron will return just those.

The column doesn't use a parameter but even columns that do use parameters behave the same way. The filtering for all of the fields is effectively broken. Is there some new system-wide setting I should know about? Is there a workaround? Or, am I just enjoying a very strange bug?

[T_Kress]

This may be a bug:  PF1-9920.  Here are details on this bug:

In Planning Registers when a column is using a Register Field that takes advantage of a control list “in Parameter Name” you will see that the filter (is Equal to or contains ) doesn’t work because it will look for the Stored value rather than the Display value”

If this sounds like your issue I would open a case to have your customer name added to this JIRA bug.

[photon]

I don't think this applies to us because filtering does work if the records are on the current page. It also behaves the same with/without a parameter and with/without a control list.

[photon · Accepted solution]

Turns out, this is a platform bug PF1-10032

Supposedly, it is a "high priority" development item but no release date is available as it's still in development.

[Oscar]

We are on Platform Release 8.2.2 and this is also an issue with Transaction Matching PV710-SV201

[photon]

It's a platform issue that affects all multi-page grids but I thought for sure it was scheduled to be fixed in 8.2.2. Good to know!

[photon]

By chance are you still seeing the issue when you use a full desktop install instead of the ClickOnce? I don't know if there's actually a difference but there's a line in the 8.2.2 release notes that says the fix for SQL filtering "will require a Windows Desktop install."

That's actually a little upsetting and not really a fix at all if it doesn't apply in the ClickOnce client. I'll open a ticket and ask for clarification. You may want to do the same.

[photon]

Support was finally able to explain the note to me. In the case of 8.2.2, the server is backwards compatible with the 8.2.1 client *but* if you don't update the client then it will still demonstrate the issue. If you use ClickOnce then, presumably, your upgrade would have been automatic. If you're still on the 8.2.1 client when connecting to the 8.2.2 server, that would explain what you're seeing.

I'm curious about your results.

[Oscar]

IT says there is a release in late September of this year 2024 that we will implement. I will report back when we implement and if the release that is installed solves our issue. As of right now, we are still on 7.3.3