Execute eval() in triggers
My use case would be to pass a field name as a text argument to a user-defined function and take action based on the field's state or value. This appears to work in the Formula field and Button, but not in Triggers.
3 replies
-
The same problem here, cloud-version-Triggers of fields are unpredictable, sometimes the code works and sometimes not. The same code in a button does work.
It looks like a delay in processing and variables coming through with incorrect data....
Have already tried all kinds of things , 'do as server' or cached() but none worked.... On my mac M1 Ninox-app they do work. Don't know what's going on....
Steven
-
I appreciate a tool that helps me complete a task, but I have to wonder why Ninox needed to create what is basically an interpreter function for their interpreter. I suspect that they didn't write the core interpreter and that it is an npm package. In this thread, https://ninox.com/en/forum/technical-help-5ab8fe445fe2b42b7dd39ee7/does-anyone-use-postman-6053aa9f78d52c6ec49c6708 , I point out the similarties in Postman. Same npm packages?
I'm not suggesting there is anything wrong with here, but I am trying to point out that if the core of Ninox is based on npm packages that they didn't author then they are reliant on those authors to update their modules. They would need to create a new fork for the module if they wanted to make changes otherwise their changes would be overwritten when modules are updated. If they created their own fork then I assume they would miss out on updates by the original authors.
Does anyone else have some perspective they could add?
Content aside
- 3 yrs agoLast active
- 3Replies
- 623Views