Table filters are not applied on mapped column value

App Building
1

Hello, we are having an inconvenient behaviour on the filter feature of the Table component.

Basically, the filter is applied to the underlying value and not to the displayed value of the column.

For instance, if we have the name column with Mapper: {{self.length <= 10 ? self: "Too long"}}

image
image1264×1004 89.5 KB

Then the result looks like this in the default table values:

image
image2002×734 48.7 KB

The issue is that the filter on the name column is applied to the underlying value instead of the displayed one:

Filter the underlying value Filter the displayed value
image
image2010×748 33.9 KB
image
image1996×732 17.5 KB

By the way, this is inconsistent with the CSV export that returns the displayed values like here (opened with Numbers):

image

Do you think it would be better to apply the filter on the displayed values or are there some edge cases ?

2

Hi @aturiot The behavior of the filter not applying to the mapped values is a bug that we're looking into :disappointed: I'll post on this thread when the bug is fixed!

3

@Tess Thank you :smiley:

4

Hi @Tess, any update on this? I am facing the same issue with my tables.

5

Hi @sean thanks for checking in! Unfortunately, we haven't been able to push a fix for this yet. :disappointed: I'll keep you posted as soon as I have an update

1 Like
6

I'm also running into this. It'd be great to have this fixed. Any updates?

7

This is now fixed! :blush: Let us know if you continue to see any issues

8

I just ran into this issue today. It's the same behavior as the original poster described.

I'm using the updated table component.

9

Hi @Tech_Hallo sorry about that! It looks like we had another bug that was conflicting with our fix for this bug. This fix should be available for you very soon. I'll update the thread when I hear more

10

@Tess Hello, curious if there is an update on this issue?

11

Hi @crhayes Thanks for checking in! I don't have a fix for this quite yet, but I'll post here as soon as I do

1 Like
12

Hi @Tess do you have any news regarding this issue?
Thank you!

13

Hi @techaf No concrete update yet! We are currently working on a significant table upgrade which should resolve this

1 Like
14

ok @Tess thank you! Do you have any predictions of when it will be released?

15

I don't have any specific timelines yet :disappointed:

I am hoping we'll have something later in Q1, but it's hard to say at this point

1 Like
16

Hello @Tess is this fixed by now or soon to be fixed?

17

Thank you for checking in! Not quite yet :disappointed:

18

Will still post here with any updates though!

19

Any update on this topic?

20

Hi @PaFi thanks for checking in! It looks like I wasn't notified properly of updates here :disappointed: We haven't solved for this in the legacy table yet, but the new table should work!