Assigned
Status Update
Comments
pr...@google.com <pr...@google.com>
aj...@gmail.com <aj...@gmail.com> #2
Hello
pr...@google.com <pr...@google.com> #3
Hello there,
Thank you for reporting this! However, it seems that this is the expected behavior as the method will return the valid named ranges. Would you be interested in turning this into a feature request instead? If yes, how would it impact your organization in terms of costs and productivity?
ka...@gmail.com <ka...@gmail.com> #4
Sure, please make it a feature request. It would be useful for automating the maintenance of named ranges across a large number of sheets, which is what I was trying to implement 3 years ago when I logged this issue. I don't know how much time is spent manually checking and fixing corrupted named ranges, but certainly some amount each week.
pr...@google.com <pr...@google.com> #5
Hi,
Named ranges help a lot to write dynamic scripts that do not require static range references. And it is crucial to have a good way to define, delete and manage named ranges within app scripts. Especially manage invalid named ranges.
Named ranges help a lot to write dynamic scripts that do not require static range references. And it is crucial to have a good way to define, delete and manage named ranges within app scripts. Especially manage invalid named ranges.
se...@google.com <se...@google.com> #6
Thank you for the details provided! I have forwarded them internally.
Best regards
ka...@gmail.com <ka...@gmail.com> #7
+1 please fix this
se...@google.com <se...@google.com> #8
I really need this feature, as my workflow often involves maintaining a collection of tabs, each having many named ranges in common. That is, I'll create a new worksheet by duplicating a "template" sheet, and then populate it with data. Older sheets eventually get deleted, which produces a growing collection of defunct named ranges.
I haven't found a way to delete them in bulk via the Sheets UI either. In fact, it's a surprisingly tedious process because the UI resets the viewport to the very top list item after each deletion, forcing the user to manually perform O(n-squared) scroll wheel rotations.
I would be really grateful if this were fixed / added.
Thank you
I haven't found a way to delete them in bulk via the Sheets UI either. In fact, it's a surprisingly tedious process because the UI resets the viewport to the very top list item after each deletion, forcing the user to manually perform O(n-squared) scroll wheel rotations.
I would be really grateful if this were fixed / added.
Thank you
ka...@gmail.com <ka...@gmail.com> #9
+1
Description
I would like to request to reactivate the function for creating new standalone Google Apps Script project using the method of Files: create in Drive API.
- What is the purpose of this new feature?
Recently, I noticed that new Google Apps Script project of the standalone script type cannot be created by the method of Files: create in Drive API (
When the new standalone GAS project is created in the specific folder by uploading the local script, the following flow is required to be run.
1. Create new standalone GAS project by Apps Script API.
2. Put the local script to the created GAS project by updating the project with Apps Script API.
3. Move the GAS project from the root folder to the specific folder using Drive API.
From now, 3 API calls are required to be used like above. This had been able to be achieved by one API call of the method of files.create in Drive API before. So I would like to request to reactivate this.