The App Sheet workflow rules are triggered on the App Sheet server when a user does an add, update, or delete through the App Sheet client and then syncs these changes back to the server.When the client syncs the changes to the server, the server first makes the appropriate changes to the spreadsheet and then saves the updated spreadsheet.You can further restrict when a workflow rule is triggered by specifying the type of update that triggers the workflow rule.For example: Changes you make directly to the spreadsheet do not go through the App Sheet server, so they do not trigger the App Sheet workflow rules.If you need help compiling/running with NUnit let me know. One comment: you have set Use Preload to true in your connection string. Use Extended Types = false; the exception changes to: System. This is a legacy feature and it's strongly recommended not to use it (it have been removed from the upcoming major version 3.0). Invalid Cast Exception occurred HResult=-2147467262 Message=Specified cast is not valid.
Sorry that it took some time to write back - my internet connection was (is) down - I've got to work via mobile...
If you need help compiling/running with NUnit let me know. Update(Data Row data Rows, Data Table Mapping table Mapping) at System.
One comment: you have set Use Preload to true in your connection string.
This ensures that any formulas in the spreadsheet are re-computed before the workflow rule is invoked.
This ensures that the workflow action has access to the latest data values.
The App Sheet server then checks whether any workflow rules should be triggered.