Did something change with casting of web request data?

Ask the community
1

Hello!

This is a fixable user error from us when building the app, but I still found it interesting enough to ask here if something changed. We have a couple of Action Nodes and comparisons that started failing recently that we were quite sure we hadn’t touched in a while. The data in the objects being updated came from web requests with the wrong data type as in this example:

{ “someNumberAsString”: “123456” }

This was mapped to an integer value in Appfarm, but when the object was being persisted we got an error like “got string, expected int”. It also evaluated a comparison with another integer as false even though they appeared to have the same value in the debug panel.

We also had a similar issue where we had mapped 1s and 0s to a boolean Appfarm value. Did Appfarm try to cast incoming values from web requests to the correct type before?

2

Hi,

This is being looked at now!

-kristian

3

Thanks!

Do you think that the old behaviour will come back?

4

Hi!

It seems to be related to Flows, so we have temporarily disabled Flows on the Standard / Stable release track while finding a permanent fix. Can you try again now? If the error is in non-dev environment, a new deploy is needed!

5

I tried in Dev now and I still get the error when persisting, value looks okay in the debug panel but seems to be a string under the hood. I did not do anything special to try to get a new Appfarm version in dev.

image
image698×196 18.5 KB

image

6

Can you try doing a minor change in Create to force a Dev deploy, and then test again? And, please also let me know the Appfarm version (as seen from the Create settings)

7

I tried to force a small change but still the same error.

image
image565×346 11.9 KB

8

I just sent you a DM!