Fixed
Status Update
No update yet.
Comments
he...@gmail.com
Hello
ve...@google.com
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?
he...@gmail.com
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.
he...@gmail.com
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.
he...@gmail.com
Thank you for the details provided! I have forwarded them internally.
Best regards
he...@gmail.com
+1 please fix this
he...@gmail.com
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
he...@gmail.com
+1
he...@gmail.com
I have run into this bug earlier this week.
Any chance of progress?
In particular, named ranges that are on a deleted sheet (tab) can hang around and do not show up through the Spreadsheet.getNamedRanges(...) call.
The Spreadsheet Editor is doing something out of band wrt the API to see these objects but from App Script I can not see them.
Any chance of progress?
In particular, named ranges that are on a deleted sheet (tab) can hang around and do not show up through the Spreadsheet.getNamedRanges(...) call.
The Spreadsheet Editor is doing something out of band wrt the API to see these objects but from App Script I can not see them.
vi...@google.com
I need this ... it's a nightmare having to do it manually
vi...@google.com
This request would break many of my scripts as we are relying on the broken named ranges not being found and we would otherwise often have duplicate named ranges with the same name. Please make it an option to also select the broken named ranges which is off by default
he...@gmail.com
Dear Google Team, this issue got reported 5 years back. Can you please let us know when this is going to get fixed
ve...@google.com
he...@gmail.com
I'm impacted as well!
Having no more options but manual deletion...
I hope NamedRanges methods get improved soon.
Having no more options but manual deletion...
I hope NamedRanges methods get improved soon.
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? User Interface, Display, or Rendering issue
When did this happen?
Dec 11, 2021 04:00 GMT+01:00
What steps would let us observe this issue?
1. Have a few notifications as bundles. (Pretty sure normal notifications won't trigger this bug)
2. Receive a few live new notifications and reply to 1 of them.
3. Expand one of the other notifications (not the one where you replied to).
4. Pull down from the top.
5. Basically do what I did in the sample video.
What did you expect to happen?
I expected a smooth pull down animation.
What actually happened?
The area from where I pulled down became blank and the notification that I pulled down was underneath that blank area.
How often has this happened?
Frequently
What was the effect of this issue on your device usage, such as lost time or work?
Slight
Debugging information
Google Play services
com.google.android.gms
Version 214218053 (21.42.18 (190400-410302452))
System App (Updated)
Android System WebView
com.google.android.webview
Version 466409233 (96.0.4664.92)
System App (Updated)
Network operator:
SIM operator: Vodafone
Filed by Android Beta Feedback. Version (Updated): 2.22-betterbug.external_20211027_RC01
To learn more about our feedback process, please visit