In the diagram, right-click on the field name that you changed, and click Rename.In the Power Pivot for Excel window, on the Home tab, click the Design View command.On the Excel Ribbon’s Data tab, click the Manage Data Model command.In the source data table, change the heading case – I changed DAY to Day.NOTE: Use this method if you need to make any future “case” changes to the data headings. Next, you’ll change the heading case again, but in a two-step process, to avoid getting an error message. The extra field should disappear from the PivotTable Field List.In the source data table, change the heading back to its original case – I changed Day back to DAY.There might be other ways to fix this problem, but here’s what I did. the new name is also listed, with a number added (Day 1).While troubleshooting the error, UniMord noticed that the changed field was listed twice in the PivotTable Field List. That error message is really confusing, and it doesn’t give you any clues as to what is wrong, or needs to be fixed. This time you should see the error message that mentions the function, PCMinorObjectCollection.Right-click on a pivot table cell, and refresh the pivot table.In the named table, change the case of one of the headings – I changed DAY to Day.Next, you’ll make a small change that causes the error when refreshing. Add a couple of fields to the pivot table layout – I put DAY in the Rows area, and Num in the Values area, as Sum of Num.Create a pivot table from the table, and check the box to Add to Data Model.Format the list as a named Excel table.Create a simple list on a worksheet, like the one shown below.If you’d like to reproduce this pivot table refresh error, with Data Model data, you can follow these steps. I’m afraid I can’t do that.” How to Reproduce the Problem Or, to misquote HAL, the computer in 2001: A Space Odyssey, “I’m sorry, UniMord. That’s it! Making that one simple change apparently caused one of the Data Model circuits to overheat, or something, and it had a little meltdown. UniMord had done one simple thing that caused the problem – he changed one of the source data headings from upper case to proper case. An unexpected error occurred (file ‘pcminorobjcoll.inl’, line 109, function PCMinorObjectCollection ::SetNameAndUpdateCollection’)įortunately, UniMord didn’t just send me a problem, and reproduction steps – he had figured out what caused the error, and how to fix it.We couldn’t get data from the Data Model. Here’s an edited version of that message, with some of the text moved, so you can read all of it.Īnd here’s a text version of the message, in case anyone is searching for help with this error message: Here’s an unreadable screen shot of the strange error – it’s one of those really wide messages, and included references that I didn’t recognize, such as function PCMinorObjectCollection. Hopefully, you’ll never run into this problem, but thanks to UniMord for sharing his information, in case you need it! I learned about this problem from UniMord, who explained how to reproduce the error in a few simple steps. The problem is easy to fix, once you see what’s causing it, but the error message, shown below, isn’t much help! I’d never heard of function PCMinorObjectCollection, had you? A simple data change can cause a strange pivot table refresh error, if you added the data to the Data Model.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |