2024.2 Upgrade - Dashboard "IN" filter quit passing data

[jdtrent (Joe D Trent)]

Hey,

The Pilot environment just upgraded to 2024.2, and now this dashboard filter isn’t passing any data through:

The filter data is in a comma-delimited list. I can display both the filter data and the row data on the screen. The filter and row data are good.

Using the condition “contains” doesn’t work either.

And it doesn’t work at this level either:

It works like this:

But not like this:

It’s filtering against other data okay, as far as I can tell.

It was working on Thursday before the upgrade.

Anyone notice this? Suggestions?

Thanks,

Joe

[hmwillett (Hannah Willett)]

Interesting.
The where clause straight up disappears from the payload if you use an “IN” operator.

I got it to work using the client filter, but that may not be ideal if you have a lot of data since it filters the dataset after retrieving everything.

*Edit–I use this a lot too, so I submitted a case under the CR: CS0004640480

[jdtrent (Joe D Trent)]

Cool. Thanks, Hannah.

[jasond (Jason Duncan)]

We are using “Contains” in a couple dashboards but they are in the Where List and they are still functioning correctly.

[jdtrent (Joe D Trent)]

Hmmm.

Moving the whereclause to the client filter worked on the first query. But when I went to the second grid, this worked:

And this didn’t.

And this doesn’t filter anything out at the provider or BAQ level (it displays all records from the BAQ):

I’m not certain about the syntax there. It’s valid as far as I can tell. ??

Joe

[jdtrent (Joe D Trent)]

Well, Pilot updated yesterday with no fix to my filter woes, so I applied the Wonder Method (I wonder if my dashboard is just bad).

I went back and generated a brand-new dashboard using one of the queries in the dashboard I’m working on. No trackers, no filters on the new dashboard.

Here’s the un-customized output:

I added this filter:

And got this output:

Just like it should.

Now I add another good resource group:

And now no output:

I can’t see that I’m doing anything wrong. Let me know if you see a user error.

Again, I’m trying to get a workaround for the “in list” issue that still doesn’t work.

I also tried CHARINDEX:

It doesn’t do any filtering:

Stumped, I am. Grateful for help, I would be.

Joe

[jdtrent (Joe D Trent)]

Oh, and LIKE matches everything too:

[dcamlin (David Camlin)]

@jdtrent

And this didn’t.

In Client filter, you can use “OR”:

Resource_ResourceGrpID = ‘ASSY’ OR Resource_ResourceGrpID = ‘EDM’

Testing with different query fields… but should work.

[dcamlin (David Camlin)]

You can also put that same expression in Provider Model “Where” clause:

Resource_ResourceGrpID = 'ASSY' OR Resource_ResourceGrpID = 'EDM'

… but you have to spell it out each time. Column = 'A' OR Column = 'B'

You can’t just put Column = 'A' OR 'B'

“LIKE” also works:

Resource_ResourceGrpID LIKE 'ASSY' OR Resource_ResourceGrpID LIKE 'EDM'

[jdtrent (Joe D Trent)]

Thanks, David.

Yep, I’ve put those things at the where list level, the where clause level, and at the client filters level with pretty much the same results.

The odd thing is that it works on ONE of the grids at the client filters level, but nowhere else and not on the brand new-vanilla dashboard.

I can’t really use the OR functionality for each resource group because I have a combo box selecting multiple “teams” with selected resource groups inside each team.

Before the 2024.2 update, that worked great. I’ve been trying to find a workaround with LIKE, CONTAINS (on the where list) and CHARINDEX, but haven’t made those work at any level either.

On the 2024.2 release notes there are 24 lines that have to do with filters, but not exactly what I’ve been wrestling with. Dunno.

Joe

[Heide (Heide Warren)]

A problem ticket has been issued for the Where clause, IN statement, in Application Studio . The problem ticket is PRB0291089 and described as "the where clause using IN statement no longer works in BAQ Options in 2024.2 (used to work in 2024.1). It states there is no work around and that the problem is submitted to development.

[jdtrent (Joe D Trent)]

Thanks, Heide.