Hi Itzier,

If you want to avoid duplicates in the TableRecords than you should eliminate it at the source meaning that you should filter your query in order to get distinct results.

Having said that there's no previous but you could achive a similiar result accessing the recordlist object through the index. So let's say you'd want to hide a row if you found the first attribute equal to the previous row.

You could do something like:





Bear in mind that with this approach you'd be hiding the row when redering but the row would still be on the table nad you'd need to adjust other factors like the record counter and pagination to compensate.

Like I said the ideal is for you to filter before binding to the widget (on the preparation).

Hope this helps,
Guilherme

Thank you Guilherme. It worked perfect.