When to use "do as server"?
I've been using "do as server" code in lots of my buttons just to make my forms a bit snappier. Unfortunately I've found that on an older/slower computer for some reason the code isn't executed properly.
The specific problem I'm having is that one of the things the button is supposed to do is create a new record on a different table. With the "do as server" code there it only creates a new record sometimes.
I've looked through the forum and found other people running into issues with this code. Are there ways to properly use "do as server"?
I should mention that I'm using the web app.
On closer inspection, one of my buttons doesn't have "do as server" code, but is still failing to create the new record in Bulk Inventory. Again, this problem is only happening on one (old) computer so far.
Just a guess but line 1 shows 2 fields. They look like a date/time field and a number (or maybe yes/no) field. In which case you are not resolving either field. As in if ‘Date/time Draining’=date value and ‘Draining? NV’= value then … Without resolving both fields the rest of the script won’t fire.
do as server - is a request to get ninox to do the processing on the server side before passing results back to the client side which saves on back and forth activity thus any processing is done quicker. That command has no bearing on creating the new record.
Well I'm blown away, do as server should not make a difference.
John - Looked at your thread... Lesson learned " Take all that I know to be true of Ninox and toss it in the bin". Have you tackled support on this mate?
I use do as server all over the place and don't get any errors (or so i thought! - now worried I might be giving customer vouchers away when I don't need to ...
- 1 yr agoLast active