Cross-link: http://www.mrexcel.com/forum/general-excel-discussion-other-questions/954352-bug-re-formula-auditing-tables-listobjects-known-ms-since-2007-a.html
I'm reporting a bug re formula auditing with Tables (ListObjects). Just follow these steps in Excel >=2007:
1.Start from a blank workbook with at least two tabs.
2.Create a table (ListObject) with dummy data on one tab.
3.Create on another tab a formula that refers to the table data, e.g., "=SUM(Table1[#Data])".
4.Select the formula cell and try to use Trace Precedents: nothing!
5.Switch tabs, select data in the table, and try to use Trace Dependents: nothing!
6.Convert the table to a normal range, and now the tracing works.
I've submitted this as SR number 116041113946418 to casemail@microsoft.com, and I'm told it's a known issue since 2007 with no plans to fix it without some kind of business justification. They write:
I mean, they're kidding, right? It's a bug in an existing feature, not a design change request for a new one that's never been in place! I was just wondering if any MVP can convince them if this better than I?
I'm reporting a bug re formula auditing with Tables (ListObjects). Just follow these steps in Excel >=2007:
1.Start from a blank workbook with at least two tabs.
2.Create a table (ListObject) with dummy data on one tab.
3.Create on another tab a formula that refers to the table data, e.g., "=SUM(Table1[#Data])".
4.Select the formula cell and try to use Trace Precedents: nothing!
5.Switch tabs, select data in the table, and try to use Trace Dependents: nothing!
6.Convert the table to a normal range, and now the tracing works.
I've submitted this as SR number 116041113946418 to casemail@microsoft.com, and I'm told it's a known issue since 2007 with no plans to fix it without some kind of business justification. They write:
The product developers have provided some feedback that they are not sure they are seeing the level of critical impact required to approve a design change request for the current version of Excel (specifically because this feature has never been in place, and therefore there hasn’t been a loss in functionality). They are looking for significance beyond that the feature would be “nice to have”. Is there significant financial impact caused by not having the feature? Is there more to add in addition to the business impact already provided, that would help the product developers understand the criticality better?
I mean, they're kidding, right? It's a bug in an existing feature, not a design change request for a new one that's never been in place! I was just wondering if any MVP can convince them if this better than I?
