Selection and filter actions do not work on the ‘Selection’ Widget

[JasonBOCQUET]

Hi, I'm having a problem with the Selection widget.

I have a Table widget with Transactions and a Map widget with Buildings. I have set up my Table widget with a message action so that when there is a Modification of record selection (i.e. someone clicks on one of the transactions in the table), it selects and filters the buildings on my map.
To do this, I set the trigger on the structure and chose my Transaction table as the trigger data and my Building Feature Layer as the action data.

So currently if a user clicks on the Transaction table and chooses one of the transactions, the building is selected on the map and the filter acts so that there is only this building on the map.

The transaction table is just a table, there is no coordinates/Feature Layer. The Building feature layer is... a layer.

Now I've got another idea in mind: I want to use the Selection widget and create a selection by attribute to act as a ‘Filter’, so I create my selection by attribute by choosing the transaction years as the Filter.
Then I'd like to set up the same type of action as I did on my Table widget, given that the Selection widget acts as a ‘Record Selection’, I want to activate this selection as a trigger and I set up my action message on the Structure and I ask it to Filter the data records by setting up the same parameter as for the Table widget: the transactions as trigger data (i.e. the one that the Selection widget selects) and the buildings on my map as action data.

The problem is that when I select my transactions via my widget, it doesn't filter anything at all on the building side.
I have a counter to see my number of buildings, and it ‘bugs’ as soon as I activate the Selection widget filter.

Could someone explain to me how this happens? And how I should set up my widget to do what I want to do?

I've followed the same logic as for my Table widget, which works. But I can't get it to work on the Selection widget.

[JasonBOCQUET]

I made some of test by adding trigger action on the table widget between transaction and... transaction himself to try to "force" the selection and it changes nothing.

Another strange point : if i try to filter (by using the selection widget with attribute selection) with the field "YEARS", and i have a result ONLY when i check "2015". On the other year, other field, other whatever, i have no result (like my screenshot)

i'm lost with this things

[JasonBOCQUET]

I've done some tests using something other than the year as a filter. Instead, I've used the name of the building, which appears in the transaction table, in order to have more precise filters that give me a single building in response rather than a huge list.

By the way, I've done a search on my Portal server logs and I've just discovered the following error:

So if I understand correctly, the problem is that I have ‘null’ IDs in my Building table?

Does anyone know how to translate this error?