Bug in behavior of selectedSourceRows (differs from selectedSourceRow)

Hello everybody,
since today, selectedSourceRows has a new behavior, and moreover the behavior ist not as described in the documentation (which it has been till yesterday).

selectedSourceRows now sends mapped values and therefore does NOT exclude mapped values, asdescribed here:

selectedSourceRow return only the source data, selectedSourceRows return (and this is new) the mapped values.

We use a table with tag fields and map over columns.

in selectedRow there are the original (not mapped) values.

in selectedSourceRows there are the mapped values.

please check the screenshots:
image (1)

We need some information about if this behavior is intended or if it is a bug.

We use 1. v3.139.0-f75171f (Build 222851)

Many of our applications are affected.

Thanks and kind regards, Kersten

1 Like

Hi @kersten Thanks for reporting this issue! Definitely looks like a regression :face_with_diagonal_mouth: I am reaching out to our team for a fix

Great! Where can we stay informed about the progress?
Thank you and have a nice day :slight_smile:

I will post here when I have an update :blush:

1 Like

Hi @Tess Perfect, thank you very much!

Please let us know, as this breaks a huge app of mine, and a temporary fix would be a huge pain.

Hello @Tess
Anything new?
Our Apps are still broke.

THanks and greetings :wave:t3:

Hi @kersten, Not much of an update yet :disappointed: We have someone looking into this bug!

Hi @Tess
Still nothing?

Hi folks,

We shipped a fix to Cloud for this issue - please let me know if you're still seeing any unexpected behavior

1 Like

Hi, it seems to me that since this "fix" the selectedRow and selectedSourceRow properties stopped working and no longer point to the actual data selected in the table.

Property 'selectedRow' doesn't work - #8 by Marius

Hello @Tess, there is an issue with table.selectedRow.xxx, in dev mode this action is working fine but in the released app, it doesn't work, the value is null.

image

1 Like

Hi @rls13 and @Maximiliano_Schvindt Yes, thank you for reporting this! Our on call team is currently deploying a fix