I continue to face issues with the Data Bindings selection window being out of sync with my flows, API calls, and Library functions. I created a new project day in 6.0.2 and am experiencing with a relatively simply page flow. The page flow looks like:
I have 2 Server Connects inside a condition statements that insert records into a database table. The Server Connects are named differently and call different API routines. I use Run statements to call cookies.set. I set the cookie based on the first Server Connect call as follows:
When I click on the Data Binding button for the value, I see what I expect to. The call to sc_insert_access_log_error, and it’s subsequent parameters. As follows:
By the way…after selecting the identify value from the First Server Connect call, and manually editing it to use the Data Binding for the Second Server Connect call, it
actually does work.
Thanks! But I did go in and manually edit the code so it works, but I don’t always know the full object path so I can manually edit it. And besides, isn’t that part of the solution low-code/no-code tools are supposed to bring to the game? LOL
Actually this is per design - because the data pickers never know how your condition will resolve, if you want to do something with the results, you should make sure that the output data generated from inside the condition has the same output name in both if and else steps.
So then you can just pick the data no matter if it is generated from the if or from the else step - otherwise you will be picking data that might not exists because of your condition.
That’s funny George, because this morning, on a different computer running 6.0.2, all of the service connection queries appear in the same screen in a Data Bindings window. (There are additional SC queries because I’ve updated the flow_startup logic.
Logic like this should be up to the developer, not limited by the development tool.
And here is another similar example. I just updated the Service Connection sc_select_cureclick logic to include all of the fields in the database table. But only the original 3 fields that were originally in the query are shown in the Data Bindings window.
That’s a totally different issue, related to a totally different part of the app and not really related to your flow condition output.
Please check: RE: Data pickers don’t reflect API Action changes
I do understand this is different but the underlying issue is the same to the developer…changes to various parts of the code aren’t being reflected ‘real time’ in other parts of the tool. Why would a developer not expect them to be? How long do I have to wait for changes to be reflected? What both of these issues appear related to is some cache isn’t being updated real-time. And until that cache times out changes aren’t being introduced. But as I’m not familiar with Wappler’s internal design structure, I admit this could be totally off base.
Thanks George, I’ve installed 6.0.3 and will report any issues.
As for the ‘by design’ issue, please explain why all of the Service Connection calls appear in the Data Bindings window today but didn’t yesterday? While I have added additional logic to the flow_startup routine, the underlying conditional logic around sc_insert_access_log_error and sc_insert_access_log HAS NOT changed, but today both Service Connection calls appear in the Data Bindings window.
And the data query changes I reported earlier is still an issue with 6.0.3. And on a different computer. As you can see the additional fields in the query aren’t reflected in the Data Bindings window.
