Get Tables working on protected sheets (add rows, sort, filter, etc.)
I would like to be able to, under the right circumstances, have the ability to add/remove rows of a table which resides on a protected sheet.
Currently if you protect a sheet you can't insert/delete rows of a table. Even if you unprotect all cells and allow inserting/deleting of rows on sheet protection, it doesn't matter and is completely ignored.
What I am proposing would have to follow specific rules:
- Table cells would have to be unprotected
- Cells below table would have to be unprotected (truly optional † )
- Insert Rows would have to be specified in sheet protection
† The way table rows are inserted is different than a standard row insert. If there are blank rows below the table it will "consume" those rows, and not shift things down. If there is data below the table, once it consumes all rows between the two, it will start inserting. This mechanism would make the second item above optional depending on how you [Microsoft] would handle this internally. My preference would be to have the cells unlocked, and honor the protection status of the cell, and not overwrite, or "consume" if there is space available.
This has been BROKEN for some time. Since we can ALREADY do this with standard cells, it should ALSO work for tables. This request has come up multiple times, and has previously been rejected as "BY DESIGN", but I'm here to tell you - and I'm an expert - this is not by design, and is a bug which has been overlooked and should be fixed.
(2016-12-07 Dan B [MS]: updated title to capture the actual ask here, which is to make Tables work better on protected sheets; currently, since protected sheets were built "before" Tables, they don't work well with "Tables" or objects that adjust/expand within the grid as users interact with them)
Thanks for logging this great suggestion, Zack, and to others for voting it up. We’ll prioritize this according to the number of votes, so if there’s more interest, please make sure to register your vote!
Lead Program Manager
Simon Hurst commented
Presumably there is no progress on this because the Access team have forbidden the Excel team from dealing with this very significant flaw in case it means that Excel can be used for basic database stuff rather than using a proper database.
It's likely that the reason you're locking the worksheet is that you're trying to protect formulas from accidentally being overwritten during data entry.
I've a number of applications wherein I use tables to collect data in columns and perform calculations on that data in other other columns. Need a way to add a new row to the table (for new data) replicate the formulas, allow a user to enter data while not allowing them to overwrite the replicated formulas on that new line.
Yatin Purohit commented
Sometimes it is not just a count of votes. Some features are required to build complex solutions. These may not be "popular" requirements fetching more votes. This is one of them. Not having this feature hampers building Excel forms (with SharePoint) in enterprise scenarios.
Tables are great but are not growing when their sheet is protected.
Conditional formatting is great but get messed-up directly by copy-paste unless the sheet is protected.
Conclusion: Tables must be allowed to grow in protected sheet to get both great functions of excel working together.
Please fix this, it’s a real must!
The post below did not work for me. In general, this is a GROSS OVERSIGHT not to consider Format as Table... feature in Protected sheets. Very common business requirement when creating any kind of form is to lock cells and formatting while allowing users to populate table.
A work around which I found was to make the table an 'editable range' in the review tab and making all of the columns in the table unlocked, other than the columns involving formulas.
Then, when protecting the sheet, ensure that 'Select locked cells' is unticked - this will unfortunately mean that the users will not be able to select or see the formulas but will allow you to sort the table.
(Although there may be a better link/ how to out there!)
Hope this helps anyone still struggling.
jeffrey Weir commented
Agree with the comment below...the lack of any response on this thread (and generally across this forum) is VERY disappointing compared to the kind of engagement we see from PMs over at the PowerBI Ideas forum. Charles Sterling is rightly proud of the level of engagement his team provides over at PowerBI Ideas. The silence here is just deafening by comparison.
Give up folks! After 752 votes from 2016 and only one response from Microsoft 18 months ago it isn't going to happen. Find the best workaround that you can. Horton hears a Who... Microsoft hears nothing.
In comparison, I employ the services of a software company in St Petersburg that respond to every email, rectify bugs and actually listen and act to customer requests immediately. Different world... the real world. Sad that Microsoft can't use the same philosophy, no matter how big and how much control they perceive to have.
hey, OMISSION, that's a big word, how about calling it an OM, nice and short. Meaning code that should have been written to do something that everyone thinks should have been done by now that hasn't been written yet. Hey MS, sort this OM, now.
Also, I think MS are balancing this request against the fact that "Professional" developers writing apps and forms etc will be using a database product or programming language that can do all this. So programmers writing code for mere Excel mortals to be able to do the same with XL are eating their own lunch and MS if they make XL able to do this are eating into their SQL server market. They are a business. That said, I think they should eat it and do this. Oh, and another thing, this forum doesn't seem to work for me in Edge.
I have voted for this and I can't wait for them to do it. However, its bugging me that people are referring to this as a bug. It isn't a bug. A bug is an error or usually unfortunate unforeseen consequence of code. This is an OMISSION. They simply haven't written the code to make tables play nicely with worksheet protection. I agree they should get on and do it, but, it isn't a BUG.
This really is a bug and a major one, no voting should be necessary.
This needs to be fixed!
Protecting the structure of a sheet from end users with limited knowledge of Excel is a basic need because the people constructing the sheets and analyzing the data are often not the same people that enter the data day to day. A protected sheet helps both with data integrity and with facilitating data entry.
Tables and structured reference are powerful tools but they just aren't an option when they stop working once you protect a sheet!
(I was so frustrated when I discovered that bug after weeks perfecting a workbook for distribution to data entry people! I couldn't believe it! I finally had to revert to "classic ranges"... what a nightmare that was!)
@anonymous below, what a ridiculous comment. Quite simply there isnt another offering that could take its place, and if you are talking about that piece of junk that Google have put out, then your comments are not worthy.
Microsoft.... please listen, respond and react. It will be your downfall if you don't. Many others have and are waiting to take your place. 3 years without a response or resolution to this issue is totally unacceptable. Resting on laurels and assuming blind adherence to your products is no longer a viable business model - you will only encourage your customers to seek alternative solutions. Wake up quickly, or die painfully.
MICROSOFT, WHY HASNT THIS BEEN DONE????!!!
This is a very important feature in Tables that is not working. Please correct this as soon as you can for us, so that we can use the Tables feature to its fullest capacity!
As Cloud services become more and more popular, this bug (yes, I consider this to be a bug) should be fixed in the very near future. We should force customers into using OneDrive, SharePoint and Teams, and such a meanwhile core feature is still not available? Tables are used as a reliable data source by Pivot, PowerBI, … and are part of a LOT of solutions; this limitation makes the experience quite poor.
I also agree on the viewers comments, till date MS should have added this feature at file protection tab check box option, as "Allow structured table =ST Expansion", Instead searching vba work around, the feature should also work with external file/sheet linked to structured columns formula, other tabs can be, "Allow Insert row/column at ST", "Expanding ST formulas from left to right"
Hopefully this will be considered on asap basis, as a normal user this would be a great functionality
Thank you in advance
Doug Glancy commented
I posted on this back in January 2016 (my post is now folded into the comments on this one). Today, with hope in my heart I tried inserting a row in a table on a protected sheet and see that it's still not possible. Are there any plans to make this happen?