Hello Ryan,
Yes; it's not the best that variables can interfere here, but, the fact is like that. So, we need to be sure that we don't use existing variable names / identifiers for the HTTP keys. Since the HTTP keys probably cannot be changed (that is, the server can expect some specific key names), it's better to change the variables names / identifiers.
P.S. If you take a look at the generated Javascript code, it's possible to see if what we are talking about is what really happend, since we can see the Javascript code and how the keys are established before the HTTP call is made.
Hello Ryan,
A couple of things. It's quite rare that you get an more or less entire different JSON payload... if you are using the same code to do the HTTP call... Anyway, I am thinking that maybe the problem is that some of the keys that you are using are in fact variables in the app, and, for that reason, we get an "undefined" for that keys...
Look at the below code, which is a test that I made here in a clean app:
The values are fakes, of course, but, they JSON payload is the below one:
... at least the keys are respected... so please, take a look and confirm that the keys that you are using are not already app variables, which may are causing the problem.
Hello Ryan,
At least to discard it, please, remove the "_Compiled" and the "_Cache" folders, then compile the app again and try it. Doing this we can assert that the code is the latest compiled one, not any possible waste in the cache... because it's quite rare... that some of the keys appear fine but no others...
Hello Ryan,
I am not sure what you understand with "monitor". If what you wanted is to debug it, please, read this new App Builder help topic, which is perfectly valid too for the current available App Builder. Basically the best is to launch the app from the IDE into an external browser, like Firefox, with the Developer Console opened. Here we can see **everything**, including the HTTP calls, params, headers, response, etc.
Hello to all,
Here is a new DecSoft App Builder alpha release, with the below changes, fixes and enhancements:
Hello Ryan,
The problem is in the [App.MilliSeconds]" variable, which must be "[App.Milliseconds]".
Hello Ryan,
Are you talking about the Report's RowClick event? If so, you no need to get the item from the Report's Data using any "index", but, directly use the Report's Record property, which contains the record which has been clicked, as you can see in the "Report" sample app, for example.
Hello to all,
Here is a new DecSoft App Builder alpha release, with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft App Builder alpha release, with the below changes, fixes and enhancements:
Hello Ryan,
Yes; both installations are intended to be compatible.
Hello to all,
Here is a new DecSoft App Builder alpha release, with the below changes, fixes and enhancements:
Hello to all,
Here is a new DecSoft App Builder alpha release, with the below changes, fixes and enhancements:
Hello Ryan,
Be sure also that you has enable USB debugging in your device.
Hello Ryan,
Yes; the USB drivers can do the trick. Anyway, try it, that is, look for it, because the debug process is faster in this way.
Everybody can read the DecSoft support forum for learning purposes, however only DecSoft customers can post new threads. Purchase one or more licenses of some DecSoft products in order to give this and other benefits.