WAI
Status Update
Comments
sa...@google.com <sa...@google.com> #2
Currently, events do not trigger when GData APIs are used to manage spreadsheet.
This is a feature request which is being discussed at
http://code.google.com/p/google-apps-script-issues/issues/detail?id=396
This is a feature request which is being discussed at
ev...@google.com <ev...@google.com> #3
This is actually a two part bug, and it isn't really a duplicate of that other feature request.
1. You'll never trigger an onEdit() function this way. onEdit works in the user's session - i.e. when I edit the spreadsheet in the browser it triggers any functions call onEdit and runs them as me.
When a GData API modifies a spreadsheet, there is no session per se, and there's no means to invoke the onEdit.
2. If you attach a Trigger/Installable Event Handler, this will ultimately catch all change events on the spreadsheet -- even those achieved via GData. The specific change function is run as the user who installed the trigger/handler, and thus is far more capable than the onEdit which runs in a sandbox.
We'll work on improving our 'edit' event comprehensiveness - but please note the distinctions above, and consider moving away from onEdit to a trigger approach.
1. You'll never trigger an onEdit() function this way. onEdit works in the user's session - i.e. when I edit the spreadsheet in the browser it triggers any functions call onEdit and runs them as me.
When a GData API modifies a spreadsheet, there is no session per se, and there's no means to invoke the onEdit.
2. If you attach a Trigger/Installable Event Handler, this will ultimately catch all change events on the spreadsheet -- even those achieved via GData. The specific change function is run as the user who installed the trigger/handler, and thus is far more capable than the onEdit which runs in a sandbox.
We'll work on improving our 'edit' event comprehensiveness - but please note the distinctions above, and consider moving away from onEdit to a trigger approach.
ti...@timdonovan.co.uk <ti...@timdonovan.co.uk> #4
"If you attach a Trigger/Installable Event Handler, this will ultimately catch all change events on the spreadsheet" - except it doesn't, and this functionality still doesn't work. Abandon hope all ye who enter here.
lo...@gmail.com <lo...@gmail.com> #5
Any update on this?
it...@arcolatheatre.com <it...@arcolatheatre.com> #6
I have a google sheet connected to an online Form+ form. The script embedded in the sheet has open, edit, and change installable triggers. None of the corresponding functions are called when data is written to the sheet by a form submission, I think because Form+ uses the GData API. I can see that the change is listed in the revision history as made by the owner of the sheet, but I think is actually made by an 'anonymous' user. Does this sound like the same issue?
va...@google.com <va...@google.com> #7
There are onEdit(e)
wont run when a script or API requests edit the spreadsheet.
This issue is working as intended according to the documentation cited above.
Description
1. Create an App Engine Python program that adds values to a spreadsheet using text_db's AddRecord
2. Create a function in Google Apps Script that will run on editing (installable event)
3.`Run the Python program
What is the expected output? What do you see instead?
The function you told to run onEdit should fire when Python adds values to the spreadsheet - but it does't. When I manually type in values, the function triggers properly but it doesn't when it adds them programmatically.
On which browser & OS?
Chrome on Win7
Please provide any additional information below.