forgot: the filter using the variable always returns an empty results set, while the explicit one returns three results as expected

@isabella.apfel @david.toro @enrique.guerr11 - any chance to help here?

Hi dear @Axel Bühler 

thank you for your question, I have tried to replicate your use case, in this scenario I'm filtering a table that contains names:

I created a view variable of type string containing the names I want to filter with:

Here is the table, where I have the column with the names and a filter in the component:

Finally you can see the output:

Let me know if this works for you!

Bests,

David

Hi, @david.toro - thanks a lot for your fast response! What you show is what I expected. But ... something is off ...

Something seems broken when then populating the variable from an attribute, seems to be about the handling of the single quotes. I added a default value (same as you did) to the filter. Below screenshot shows no value selected, so current value = default.

I had to rebuilt the table from scratch - no idea why - it now works with the defaults BUT it doesnt work when I assign a value from an attribute to the variable ... and if you check the value of the variable you suddenly have the backslashes ...

Regards

Axel

@Axel Bühler 

I have extended the setup to include an input dropdown with multiple selection that writes to the variable, as you can see the output is as expected.

Can you check if this setup works for you too? Else I'd propose to reach out to support to dig deeper on what is causing the issue.

PD: Something you might want to check, is making sure that in the input dropdown you use the option "Load items" and select the table were the items you want to filter with are. As you can see in my setup each item is a row on that table, I think you might have multiple items per row appended in a string, this does not work.

Bests, David

Hi, @david.toro 

thx for getting back - I rewrote the data model and created linking tables - this solution works but needs more effort in data integration.

It might be interesting to think about how to enable pulling a string from an attribute value that serves as PQL code. In this case an attribute value would serve as the list of items that can be used in the table.field IN ('yyy','ZZZ') statement - 'yyy','ZZZ' could be pulled from the attribute value.

As an extension to this idea you could also consider to enable selection of a single record and storing it in an object variable - this could allow for easy access to all attributes of the selected record and using them for e.g. filtering.