#Eventscripts parallel processing install#

For this situation, I used CacheService like the channel of golang.value is sample, myFunction: myFunction was done. When I put sample to “A1”, onEdit: onEdit was done.When the result from myFunction() was retrieved, each result is summarized and show it. At onEdit(), after own task was done, it waits for retrieving the result from myFunction().At myFunction(), after own task was done, it puts the result using CacheService.In this sample, Utilities.sleep(t) was used as the task.These functions work as the asynchronous process as mentioned above. onEdit() and myFunction() are run by the simple trigger and the installable trigger, respectively.formatString( 'onEdit: %s, myFunction: %s', 'onEdit was done. When a cell is edited, the script is run.This script works at the container-bound script of Spreadsheet.

#Eventscripts parallel processing install#

Please install the trigger to myFunction() as the “On edit” trigger.

In this case, each task is summarized after each worker was finished. The sample script becomes like the script which was used at the section of “Simple Triggers and Installable Triggers”. In this case, each task is completely independent. Sample situations by the asynchronous processing using event triggers are as follows. log( 'myFunction: ' + start + ' - ' + end) log( 'onEdit: ' + start + ' - ' + end) Ĭonsole. sleep( t) // This is a sample task.Ĭonsole. By this, it is considered that the simple trigger and installable trigger work as the asynchronous process with the 2 workers which are ```onEdit() andmyFunction()``. As the result, it was found that the start and end time from both functions were almost the same. When the event trigger of on edit was run, it judges whether both functions worked as the asynchronous process by confirming the start and end time. At both onEdit() and myFunction(), the start and end time are output after Utilities.sleep(t) was run. myFunction() was installed as the trigger of “On edit”. Simple Triggers and Installable TriggersĪt first, it investigated about the work of simple trigger and installable trigger.

Install myFunction() as the trigger of “On edit”.īy above setting, when the cell of spreadsheet is edited, both onEdit() and myFunction() are run as the asynchronous process.

myFunction() which is used as the installable trigger is put in the project.

onEdit() which is used as the simple trigger is put in the project.

Create a project as the container-bound script in a Spreadsheet.

Simple triggersįor example, when the event of on edit is used as the asynchronous process, it uses the following flow. So I investigated about this situation.Īs the result, it was found that the following simple triggers and installable triggers work as the asynchronous process. When I thought about this situation, I thought that both onEdit() which is run by the simple trigger and the function which is run by the installable trigger might be able to be used, simultaneously. The functions of simple triggers which is the same events are not used in the project. In order to avoid this, the installable trigger is installed to the functions except for the functions of simple triggers.

If the trigger is installed for the function of onEdit(), when the event trigger is run, onEdit() is run 2 times. When users want to use the script including some methods which are required to be authorized as the onEdit event, a installable trigger of onEdit is used. OnEdit() which is a simple trigger is often used as a trigger when the values are modified on Spreadsheet.

This is a report about the possibility of asynchronous process using event triggers.