Peter Barfield Posted July 11, 2015 Posted July 11, 2015 receiving a 101 error on pulled payoad (which is a missing record). if i run under full access account no problems but accounts that are not full access get this error any thoughts.
Jonathan Myrah Posted August 7, 2015 Posted August 7, 2015 Hi Peter, any luck with this? My users just started to get this same error a couple of weeks ago and I can't figure out why. Thanks!
Peter Barfield Posted August 9, 2015 Author Posted August 9, 2015 Jonathon, The problem in my instance was a script not having privileges. On face value all scripts that needed to run under full access where correctly set however, I found 1 script which was referencing from within another script that the user did not have full access on. Changed the script to run under full access privilege and all works well now. Hope this helps.
Jonathan Myrah Posted August 10, 2015 Posted August 10, 2015 Thanks Peter. I've gone through all of the scripts looking for that, but I will double check them. Here's hoping...
Jonathan Myrah Posted August 10, 2015 Posted August 10, 2015 The permissions look good on all of the sub-scripts as well. Here is a screenshot of where the error is happening in case it sparks any thoughts...
Jonathan Myrah Posted August 10, 2015 Posted August 10, 2015 Found it! I had recently added a new table to the syncing relationships and missed checking the box to "Allow creation of records in this table via this relationship". All is good again
Peter Barfield Posted August 10, 2015 Author Posted August 10, 2015 Good to hear. It's quite a lot of detective work at times and sometimes the simplest of things we miss.
Recommended Posts
This topic is 3662 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now