Perspective Table filtering but not passing any data

Hi folks hope someone can help,

I have created a table which based on the user, filters and displays their items.

I have an expression len({../BreakpointContainer/Table.props.filter.results.data}) which gets the amount of rows filtered per user, this then makes visible the right amount of charts containing the user previously entered values.

I was using a dropdown box during development to allow selection of different users. This was working until I tried to bind the props.filter.text field of the table to the session.props.auth.user.userName.

The userName passed back is correct (I have it showing in a label) and the table is filtering the right amount of items for that user.

The problem is that the expression to read the length of returned rows is reading zero until I click on the Item column in the header. Then the expression works and everything populates.

tab2

(when I click on the table header)

tab3

Would anyone know why the expression is 0 until I click on the table header.

I am using Version: 8.1.35

Regards
Richard

I can't reproduce the problem.
Just a thought, but the table "virtualized" property sometimes does strange things. Try toggling that.

Tip: Left-align columns of text. Right-align numbers. e.g. guidelines - Should content be left aligned or right aligned in a table that contains a mix of text and numbers? - User Experience Stack Exchange.

@Transistor thanks for your reply.

I have toggled the "virtualized" property and set all columns as you have suggested but still the same problem.

I reverted back to using the dropdown box and the problem disappeared, but I need to get it woking using the userName of the user.

It looks like the userName has been passed to the table where it has done the filtering, but it seems like it hasn't completed the process so the expression still thinks its 0

Regards
Richard

After @Transistor couldn't replicate the problem I duplicated the table and redirected the tags/binds and tried it.

It worked, appears something must have been corrupted with the original table.

I have this working now.

1 Like