Wappler 7 V14 - Server Data Bindings Set Value Contains Incorrect Subfields

[Antony]

Wappler Version : W7v14
Operating System : Windows
Server Model: PHP

Expected behavior

What do you think should happen?

In the server data bindings, a Set Value should not have any sub-fields

Actual behavior

What actually happens?

They sometimes do. See this example: the Set Value is expandable with a range of subvalues that are actually from a previous database query.

[mebeingken]

@Antony

In the server data bindings, a Set Value should not have any sub-fields

I’m going to disagree with this part (although I’m sure your bug report is valid). If I assign an object to a set value (I often do), it would be logical for the object structure to be passed through to the data bindings.

[Antony]

I would agree Ken... but as you can see, this Set Value can only have the values of 0 or 1...

[Quy]

"Set Value" actions turn into a expandable item with options as if repeat

Latest Wappler, Latest MacOS I have added a library action and also duplicated it to created a simpler version derived from it. I noticed that when adding a set value action and setting the value and wanting to use it in another action for instance “Insert” the set value turned into an expandable item with options as if repeat. I have never had this before: [Screenshot 2022-09-18 at 11.16.18] [Screenshot 2022-09-18 at 11.16.03]