The "library solution" is actually your best bet. It is not as complicated as it sounds, but it takes a little bit of one-time work.
First you create your script in one spreadsheet (let's call it the Master spreadsheet).
Save a version of the script by clicking File → Manage versions in the script editor, and give your version a name:
Close this ...
Publish your script as an add-on. Bear in mind that you could make it public unlisted or private, shared with a Google Group.
The Script Gallery was replaced by Add-ons that were added on 2014.
In order to publish an add-on you should paid a 5 dollars fee to be able to publish an add-on to the Chrome Web Store G Suite ...
There are two basic categories of Apps Script files -
Bound to the document (Sheet, Doc, Form)
Bound files do not show up in your Google Drive. Stand Alone Apps Scripts files do show up in your Google Drive.
You can create multiple projects inside of an Apps Script file, but projects in other files can not be searched or loaded into the code ...
According to Eric Koleda in Code.gs - date_add_and_subtract to make available the custom fuctions in an add-on it's required to include at least one add-on menu, but this is not working at this time.
There are a couple of related GAS issues, please star them:
"Test as add-on" from standalone project to Google Sheets doesn't link ...
You should try Google Clasp which is talking about
The Drive ID of a parent file that the created script project is bound to
Did not tried but looks like there are commands for retrieving project script code, create and update :
Pull: Fetches a project from either a provided or saved script id. Updates local files with Apps Script project
Push: Force ...
Thanks to Rubén's comment, I looked at the execution transcript, and found this error:
[19-11-28 15:11:32:379 PST] Starting execution
[19-11-28 15:11:32:498 PST] SlidesApp.getActivePresentation() [0.114 seconds]
[19-11-28 15:11:32:570 PST] Execution failed: Authorization is required to perform that action. (line 6, file "progress") [0 seconds total runtime]
I use this option to install my Gmail add-on on the Google accounts I use while on development, prior to publishing.
Check-out this link https://developers.google.com/gsuite/add-ons/how-tos/testing-gsuite-addons#install_an_unpublished_add-on
I don't know how it works for editor add-ons, but for my Gmail/Gsuite add-on, it's pretty straightforward. I can use ...
Halfway is to download the files from your project.
I found a tool to achieve this:
by kerem tiryaki
You have to give access to your drive
to find the script, you'll have to copy the key of a script:
GoogleAppsScriptExporterForAll now has access to your Google Account
Publish a Google Add-on to the G Suite Marketplace
You must use the G Suite Marketplace SDK in order to get to the
“Publish” section for publishing an add-on, and you must first open
the Google Cloud Platform for your specific project (apps script
The G Suite Marketplace SDK must be enabled in the Google Cloud
The two ...
A Google Apps Script web app will have it's own URL to be used to make HTTP GET/POST requests.
A G Suite Add-on adds a menu to a G Suite app (Google Docs, Google Forms, Google Sheets, Google Slides)
A Google Apps Script project could be bounded or standalone and could be used to post a G Suite add-on, a web app or both.
I tried to publish it with "Private visibility" but that didn't make it available to my other documents (tried searching in Add-ons > Get add-ons).
So how do I make the script available to use in all my documents?
Publishing and add-on as privately (unlisted or limited to a group of users) will not display the add-on on the add-ons store, except for ...
According to https://developers.google.com/gmail/add-ons/how-tos/publish to allow other users on your domain to install your add-on you should give them the deployment ID.
Publishing Gmail Add-ons
Publishing add-ons allows them to be used by other users. While a few
add-ons have been made available in the G Suite Marketplace for users