Under Server-Events -> Table-Specific -> Row_Updated and Row_Updating is custom code to manipulate data while a user is trying to save it to the database.
The code in there was tested with an administrator account. On the administrator account Master/Detail Edit works as it should but on a a non-admin sales account trying to save a Master/Detail Edit results in a failure binging the client to the Master/Detail View page with a generic red toast notification that says Error No Records Found.
Sadly there is nothing notable logged to the client console, the server console, or in the server logs.
I put a Log("Row_Updating"); and a Log("Row_Updated"); at the top of their respective sections and Row_Updating is logged but Row_Updated isn't. This led me to believe the error is somewhere in Row_Updating but I also put one at the bottom of Row_Updating and it was logged as well. This leads me to believe everything in Row_Updating is running fine and the failure is located elsewhere but I don't know where to look. Is there anything that could be between Row_Updating and Row_Updating?
Is there a better way to debug this?