I have made an add-ons for Google app scripts . Now I want to add it in every document in one folder. How can i do that?
In this tutorial https://developers.google.com/apps-script/quickstart/docs, it only uses for one document.
If your add-on was published to Google Marketplace/Chrome Web Store and you installed it from there, and you are the owner of all the docs in the folder, that add-on should be available in your docs under Add-ons menu. I think it's the same for domain-specific add-ons as well (have no way to check it at the moment).
If you just created an add-on in a doc-bound script, then the add-on will only be available in that doc. To add it to other docs, you will have to copy your script into those docs manually - there is no API way to do it.
Related
I wrote an extension for Google Docs that used to show up in the Add Ons menu for my organization. The add on no longer shows up in the menu, but I can see it in the Google Workspace Market. I originally had it on the Google Chrome Webstore, but then it moved to the Workspace Marketplace. I can also see the corresponding project in my Google Cloud Platform console.
However, when I go to the Google Apps Script Editor, my project is not there. I have no access to the source code or ability to fix it so that it will show up in the Add Ons menu again. Does anyone know where I might be able to find script? I have the URLs for the Workspace Market, but it is private to my organization, so no one will be able to view it.
Also, I tried going through Google Support but they said that App Scripts is not supported and to ask on Stack Overflow.
Edit:
Screenshot of error
Answer to rev 1
Open the Google Marketplace SD settings page on the Google Cloud project linked of your add-on. There you should find the script project id.
Then on your web browser open your Google Apps Script project by writing a URL like this:
https://script.google.com/d/<<put-here-the-script-project-id>>/edit
If the above doesn't work, see notes at the bottom
Resources
Publish an add-on
Enable and configure the Google Workspace Marketplace SDK
Related
How can I view the source of a google apps script Library
Library with identifier underscoreGS is missing
NOTES
If you get the message "Sorry, unable to open the file at this time", try again using Chrome on incognito mode with all the extensions disabled and signing in only with an account that has access to the Google Apps Script project.
If the above doesn't work either, follow the screen advice, wait a bit and try later.
Related
Google Drive Page Not Found - Sorry, unable to open the file at this time
I have read some documentation about the notion of "installed or enabled editor add-ons" but I didn't understand very well. I have developped an add-ons that work with a specific google sheet template. The rule is that I will make some copy of the sheet model and distribut them to collaborator or they will do themselves the copy of the model and work on it.
I would like to know if it's possible to link the add-ons to the doc and in that way my collaborator don't need to search the add-on on G-suite store because ideally the copy of my google sheet template will offer the possibility to install the linked addon directly in the menu of the google sheet.
Finally from what i understood here,https://developers.google.com/gsuite/add-ons/concepts/editor-auth-lifecycle
Authorization model
Two properties of editor add-ons make them especially easy to share and use:
Once you get an editor add-on from the store, you see it in the Add-ons menu for every
you open or create. Collaborators on those documents won't see the add-on except in documents
where you actually use it.
Once you use an editor add-on in a document, your collaborators also see it in the Add-ons menu,
but just for that document (unless they have also installed that add-on).
I would like to have the second exemple and not the first.
Thank you for your answers guys
I have developed a google sheet addon, I had succefully published that add-on from Google sheet bound script ie from tools->Script editor.
But If I made direct google apps script project(standalone project),I am unable to publish it,And a notification is popped up.
I research that I need it to setup it from google console,to publish standalone google app script to add-on ,But I don't found exact options to proceed.
The instruction is a very confusing for a first timer. Google keeps redirecting you to the page describing publishing editor addons, but what you really need is the page describing how to create a project on cloud platform.
https://cloud.google.com/resource-manager/docs/creating-managing-projects#creating_a_project
Steps:
Create Project and get Project Number using instructions from link above
Go to you script. Select in the menu Resources > Cloud Platform projects... and enter your project number there
Then google will ask you to setup OAuth
After that, you can move your script to cloud platform and publish.
To publish an addon for G Suite Document editors follow the instructions here
https://developers.google.com/gsuite/add-ons/how-tos/publishing-editor-addons
The specific part about the GCP project is
Technical
The add-on script project must use a standard Cloud Platform (GCP) project. If the script project currently uses a default GCP project, you must switch to a standard GCP project. All collaborators working on the add-on should have access to the standard GCP project.
I've been trying to create a Google Spreadsheet plugin from some existing Google App Scripts that I have, and one important part of this app script is Custom Functions.
Though the documentation for the add-ons doesn't indicate that this is supported, the documentation for Custom Functions does indicate that you can.
https://developers.google.com/apps-script/guides/sheets/functions
Through testing, I have not once been able to get Custom Functions exposed through a add-on. Does anyone know the secret sauce to get this to work?
Answer
According to Eric Koleda in [Code.gs - date_add_and_subtract]( https://github.com/google/google-apps-script-samples/blob/master/date_add_and_subtract/Code.gs) 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 on testing mode.
NOTE: The originally referred page was removed but the Date add and substract add-on sample code is available at https://github.com/googlesamples/apps-script/tree/master/sheets/dateAddAndSubtract.
The "solution" to test a custom function add-on is to publish the add-on privately so you could avoid the Google review of an untested add-on. Related Q&A: Publish an add-on privately
NOTES:
You have to create a Google Cloud Project, set OAuth Consent Screen, add the Google Workspaces Marketplace SDK, complete the configuration page, the listing page and to publish the add-on
Setting the OAuth Consent Screen for Internal Use requires to a Google Workspace Account
Setting the OAuth Consent Screen for External Use limited to test account only doesn't allow to publish the add-on to the GW Marketplace.
One scenario is to use different Google Cloud Projects for testing and production but use the same Google Apps Script project. Another scenario is to have two different Google Apps Script projects each one with their own Google Apps Project and someway copy the code from one to the other i.e. using Google Apps Script GitHub Assistant Chrome Extension, CLASP or the Google Apps Script API.
Remarks
There are a couple of related GAS issues, please star them:
"Test as add-on" from standalone project to Google Sheets doesn't link custom functions
After activating an add-on, custom functions get stuck Loading... until spreadsheet refresh
I have a document container-bound script, that I would like to publish, I would like to make it available to people in my google apps organization. I know the script gallery is only available to spreadsheet apps, so how do I publish it. Or, more specifically, currently the script is bound to one document, how do I make it run on all documents? My user base is fairly small, about 300 people, and I can have each one of them install it if need be.
Thanks,
Ari
There are limited options for distributing container bound scripts. When a document with a container bound script is copied, the script is also copied. So if the 300 people in your organisation copied the document they would also have a copy of that script. The issues with this techniques is that the script is only attached to that particular document and creating a new document, rather than taking another copy of the template, or opening an existing document will not include your script functionality. The other issue the script in the copies of your template becomes orphaned and you cannot push updated versions. Using Managed Libraries addresses this to a degree but the end user still needs to select the newer version of the script in the script editor.
A way to mass deploy your script in your organisation is using Google Apps Script authored Add-ons. Add-ons are installed by users and become available to every document they work on. The script behind add-ons can also easily be upgraded without any user intervention. One issue with this approach is all add-on's need to be approved by Google. This introduces a risk that Google will not publish your script as an add-on. Whilst there is a public store of add-ons after your project is approved by Google there are visibility options to restrict access and prevent there general visibility. As per add-on publication step #12:
In the "Visibility options" section, select which users will be able
to find your add-on — usually either all users or only users with an
account in your Google Apps domain.
Hopefully when add-ons leave developer preview Google Apps domains will have more control over publication and visibility (I've opened a feature request for this)