Refresh Pivot Bug in Power Query version 2.16.3822.242

I have an Excel file with Power Query and several Pivot Tables built from the Power Query data. The Pivots are built from the table loaded to a worksheet, and there is a timeline date slicer connected to all those various Pivot Tables.
In build 2.16.3822.242, refreshing the Pivot Table (either by right-click/Refresh, or programmatically via macro) causes the date timeline slicer to disappear (literally be deleted from the sheet). The Pivot Refresh succeeds fine.
This does not occur when using Power Query Version: 2.16.3785.242. So for the time being, my only workaround is to avoid installing the newer build.
Any ideas what's causing it? I told my coworker (the primary user of the file) that she could still use the file and go filter every pivot's date range separately, rather than the slicer, but that is laborious and for now she is just going to remote-desktop
into a computer that doesn't have build 3822 installed yet.
Shawn Keene

Hey Ed, I apologize for un-proposing your answer so quick, I was on my Windows Phone but the forum loading spinner wouldn't leave the text entry field, so I couldn't input a reply until I got home.
I actually found a solution just today. This may not be the 'only' solution, but it worked well. When I had previously thought I had a solution, it only 'worked' because my subsequent refresh after making the table change didn't add any new rows of
data (all the rows it would have returned that day were already there). Today I made the change and then refreshed, and the new rows were formatted as the Power Query intended them to be.
The settings I used were to set the table to "do not preserve formatting" and to "overwrite existing cells for new data, clear unused cells". Now my inserted Power Query table is plain white (no banded lines or colors), but I don't care
because it's on a hidden sheet that no one will ever see.
Here's the table settings that seemed to work well for me.
And to be honest (although I haven't extensively tested), I think this was only a problem if the table was created using an old version of Power Query, then refreshed with the new version. Anyway, now I can easily refresh my Query and then the Pivot
from it without trouble.
And since I suck at brevity: I also think it'd be beneficial for me to re-create these workbooks and have the Power Query only add the data to the data model, and source the Pivot directly from that, rather than indirectly source the pivot from a populated
table. Basically save a step, and then the Pivot will refresh together with the connection, rather than having to be refreshed separately after the query is done.
In any case, I'm loving this tool and I'm practically a Power Query evangelist to every other department, because it empowers the knowledge worker to investigate data without waiting weeks for a DBA to have time to write a query and send results. Plus
we power this awesome real-time performance dashboard showing live KPIs of 15 metrics, and ditched our Domo.com account, saving upwards of 100k per year, just by using Power Query. Using nothing but plain Excel and Power Query, it publishes the graphics to
our intranet and TVs around the builds live all day. It's amazing.
Shawn Keene

Similar Messages

What's New in Power Query Version 2.14.3722.242 ?

Does anyone know what's new in Power Query 2.14.3722.242 released yesterday, July 30th?

Btw, subsequent to David's assist (above) I discovered this ... 6 new updates in Power Query - July 2014

Automatic Refresh of a Merged Power Query giving 'Table Not Registered' error

Scenario: I have 5 tables in my Azure VM SQL database associated with my ERP system. I have loaded all 5 tables into a 'Build Excel' workbook, merged the tables together and created a dataset that my users will be using. From that 'Build
Excel' workbook - I published to the BI catalog a data set simply called 'Customer information and Statistics' - This is searchable by my users and they don't have to go through the effort of combining the 5 tables.
I have a published workbook that uses the 'Customer Information and Statistics' data set and nothing else. I tried to schedule a refresh of the data and it failed (below is the error when I did a manual refresh):
OnPremise error: Sorry, the data source for this data connection isn't registered for Power BI. Ask your Power BI admin to register the data source in the Power BI admin center. An error occurred while processing table 'Customer Information and Statistics'.
The current operation was cancelled because another operation in the transaction failed.
So, going down that rabbit hole, I began the process of 'registering' this in Power BI - however, when I copied in the connection string it began walking me through a process of providing credentials to the 5 tables in my SQL server - that are already exposed
in my main data Sources. I figured I would continue and tried to use the service account credentials that my main data sources use and it would not properly authenticate.
Taking a step back it prompted a few questions:
Why am I being asked to register these 5 merged data sources that are already exposed in my base data sources?
Is my approach of creating 'Friendly named' Merged datasets for my users an incorrect approach?
Is there a different method I should be using to establish autorefresh on Merged datasets in these published workbooks using Power Query?
Thanks for the help -
Tom Grounds

Tom, can you submit this as a bug in the UI via the Smile Frown button?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

I found a bug in Power Query. Anyone know why this occurs?

It took some time to isolate the cause of this.
One of our SharePoint sites couldn't successfully be connected to with Power Query for Excel 2013. We would receive this message: "DataSource.Error: OData: The feed's metadata document appears to be invalid."
I made a site template and started making copies of the failing site in order to test the cause of the error.
I narrowed it down to 16 lists that, if present on the site, would cause the connection to fail. Those lists' names were simply numbers. For example: "1", "2", etc.
I noticed in the Listdata.svc feed for the site that only the choice columns were included in the metadata and not the single line of text column names. In Listdata.svc, it appends a "c_" in front of the both the list and choice column
names if the list name starts with a number.
After many tests I believe I have confirmed you cannot start the name of a list with a number IF you have a choice column in that list. Anyone know why this is?

Hi,
Thanks for reporting this issue. Would you be able to capture some Fiddler traces and send them our way so we can take a closer look at the underlying errors?
Feel free to send them via "Send a Frown" in PQ for privacy.
Thanks,
M.

Power Query Update 2.16.3785.242 (64-bit) has Corrupted Excel

The most recent update to Power Query has rendered Excel useless. Any use of the Ctrl key (copying, pasting, etc.) will cause Excel to crash and restart.
A co-worker had the same problem yesterday and we were perplexed in its origin, though it became clear the update was the source after updating this morning.
We need a fix ASAP!

Hi W. If you can still repro the crashes, can you please do the following to get a crash dump and then send it to us? (You can use the Send a Frown functionality on the working version of PQ.)
Edit the registry, open the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting and change the DWORD value ForceQueue to 1
Open %LOCALAPPDATA%\Microsoft\Windows\WER\ReportQueue in Windows Explorer to monitor it
Reproduce the crash – at this point something should appear briefly in the ReportQueue folder
Thanks,
Ehren

Pivot Function in Power Query

Hi all,
One thing i'm struggling with is the use of the pivot function to pivot a column within PQ. I'm confused on why this happens and why I can't clear it up...but here goes:
I unpivot a set of columns which then gives me two columns (Attribute/Value). I do this because I have repeated columns of data, but it should all fall under one column (think Hours, Hours1, Hours2, etc) - basically the input is coming from a form
that has repeating fields but everything is the same data type.
I make some adjustments to the Attribute columns (Replace items within the Attribute column) then Pivot the two columns again...theoretically I would be able to do this since i just unpivoted the same data, but:
I get tons of errors (usually "There were too many elements in the enumeration to complete the operation".). I'm not entirely sure why this happens and it doesn't seem to make sense to me that I can't UnPivot and Pivot and get the same results
as I originally had.
Any recommendations would be greatly appreciated!
EDIT: I'm choosing "don't aggregate" during the Pivot operation...I get values if I keep some sort of aggregate function, but not the right values (I get a count of the fields instead of the data within the fields)

Try this solution:
Once you are to step 3, add an index column that starts at 0 and another index column that starts at 1.
Transform by Pivot Column using the names in Attribute to create new columns and the Values Column set to Value. Under advanced options select Don't Aggregate.
Fill Down the Date column
Filter rows to remove null from Work Time.
Here's the M code from the advanced editor:
let
    Source = Excel.CurrentWorkbook(){[Name="Table1"]}[Content],
    #"Added Index" = Table.AddIndexColumn(Source, "Index", 0, 1),
    #"Added Index1" = Table.AddIndexColumn(#"Added Index", "Index.1", 1, 1),
    #"Pivoted Column" = Table.Pivot(#"Added Index1", List.Distinct(#"Added Index1"[Attribute]), "Attribute", "Value"),
    #"Filled Down" = Table.FillDown(#"Pivoted Column",{"Date"}),
    #"Filtered Rows" = Table.SelectRows(#"Filled Down", each ([Work Time] <> null)),
    #"Changed Type" = Table.TransformColumnTypes(#"Filtered Rows",{{"Work Time", type time}})
in
    #"Changed Type"
If that doesn't work, this example might do the trick:
http://www.excelguru.ca/blog/2015/01/07/transpose-stacked-tables/

New SP Custom List results in Power Query Error: Expression.Error: The key did not match any rows in the table.

Hi,
I'm running into something that seems to be a bug in Power Query. I've got my Power Query tables from SharePoint lists into Excel and Power Pivot data model. (Making sure the SharePoint site is in English and I replace MMD columns with normal columns).
But then, when I close down Excel, add another custom list to SharePoint, open the Excel workbook and want to add that new custom list using the same connection (via recent data sources).
It shows the newly added custom list in the explorer but with an error:
Nothing I can do to fix this; restarting Excel or PC; nothing.
The only way I got around this was by removing all my existing data sources and re-create them..
after that, the same SharePoint custom list WAS read with Power Query without an issue.
Thanks,
Jeroen

Its because of recent updates to Power Query.
In recent updates internally their is some change in syntax for reading particular table from list (I faced this issue while reading data from Excel file, i.e After applying recent update of Power Query my Queries which were working fine before starting
throwing same error that yo are facing).
As solution their is small tweak to be done in existing queries, instead of recreating all queries. If you can provide me your complete old query from Advanced editor then I can point to tweak that need to be done.
Thanks,
Sagar K

Sharepoint 2013 support for power query

Hi,
I wanted to know whether SharePoint 2013 supports power query and can we refresh power query data from excel services.
Thanks,
Bhawna.

Hi Bhawna.,
According to your description, my understanding is that you want to know whether SharePoint 2013 support Power Query and refresh power query data from excel services.
The refresh of workbooks involving Power Query queries isn't currently available in SharePoint 2013.
Here are some similar posts for you to take a look at:
http://social.technet.microsoft.com/Forums/en-US/62b6384e-3120-40e2-9469-01c808530f55/does-sharepoint-2013-have-power-query-services-similar-to-power-pivot-and-power-view?forum=powerquery
http://social.technet.microsoft.com/Forums/en-US/2da77984-5a97-4102-9119-97ecbc39f527/publish-power-query-workbook-to-sharepoint-2010?forum=powerquery
In addition, I am not an expert for Power Query, you can create a new thread on the Power Query forum, more experts will assist you with this issue.
Power Query forum:
http://social.technet.microsoft.com/Forums/en-US/home?forum=powerquery
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Power Query import data error

Hi all,
As Power Query does not support ODBC I tried direct connect to DB via menu
From Database/From MySQL Database.
I passed authorization and my query was being running.
But after all records were downloaded I just got error
'SELECT command denied to user '****'@'x.x.x.x' for table 'bogus_table' and
as result PQ query was failed.
What's interesting is that my original query was 'SELECT id FROM b_user'.
I do NOT query any 'bogus_table'.
What does all that mean?
-- Paul

This appears to be a bug in the MySQL ADO.NET driver. Under some circumstances, when you close the DbDataReader, the MySQL driver will attempt to run the query “SELECT * FROM bogus_table LIMIT 0”. It attempts to trap the error by checking for error number
1146 (table not found), but in this case it’s getting a different exception – probably error number 1142 (select permission denied).
You should
1) Report the bug to MySQL.
2) Delete the table named bogus_table, if it’s not actually needed.
3) Consider renaming the table named bogus_table if it is needed, or granting select permission to all users.
We're sorry you had to run into this, but even if we could mitigate this MySQL bug in Power Query code, it would take nearly two months for you to get the updated version. Fixing the local data is likely the best approach.

What's new in Power Query January 2014 update?

I just downloaded Power Query Version 2.9.3547.162 (January 2014) and I'm wondering what's new.
The
What's new in Power BI page does not display any news.
Thanks!

December is typically a slow month at Microsoft for all the obvious reasons. Because of that, we decided to focus on bug fixes and other product quality improvements. Over 250 product issues were fixed in this release.
There were also significant improvements to the Text/CSV import experience to automatically detect column delimiters.
One subtle change might take some getting-used-to -- or at least it did for me: the advanced editing dialog is now accessed from the "View" tab on the main editing dialog instead of being a mysterious button on the formula bar.

How to disable update notifications for Power Query?

Is there a way to disable the notification of available updates for Power Query? Command line switch on install, anything?
Thanks!

it was included in the Power Query version released in September 2014. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Power Query for Excel DisableUpdateNotification dword 1 will disable the update notification.
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or MVPs.
Twitter:
@alexverboon | Blog: Anything About IT

Power Query SCCM Installation

I have been trying to create a SCCM application which will install Power Query after installing MSOffice Pro Plus 2013. On a machine which has the Office, I can manually install Power Query, however, silent and administrative installs do not work.
Has anyone successfully install Power Query through System Center as a system application (no user interaction)? If so, what am I missing.
Steps taking so far:
Downloaded latest Power Query Software: "PowerQuery_2.13.3688.242 (32-bit) [en-US].msi"
Created a new application from the MSI.
Created a deployment.
Tested deployment on Windows 8.1 Machine. Failed to install.
Tested deployment on Windows 7 Machine. Failed to install.
Tried on both Windows 7 and 8.1 Machines to install by command line (admin command prompt) with /a or /I with /qn and will not install.
In event viewer return code is installation success or error status: 0.
Verified com add-in is not present.
Tried on Windows 7 and 8.1 machines installing with no flags and installs successfully.

Hi,
I've tried to install PQ through SCCM it failed. I'm using command: msiexec /i "PowerQuery_2.16.3785.242
(64-bit) [en-us].msi" /q ACCEPT_EULA=1
This command works when I run cmd as Administrator on local machine (non-domain joined). But when cmd runs as a regular user (this user is local admin) it fails. SCCM tries to run it as local admin.
SCCM gives following error: 0x643 (1603).
Google says that it is related with elevation. Note: Run as Administrator feature blocked on client machines through GPO.
Could someone help me?

Update to power query does not refresh the pivot table

Hello all,
whenever i make a change to power query dataset and do a refresh, the data will not be refreshed on the pivot table build on the power query dataset.
Is there anything which i missed while updating the powerquery?
Thanks
Satya

I have created the Powerquery dataset and loaded it into Data model. Then i have created the pivot table using the external connection.
After making changes to dataset and then loaded the dataset to Data model. After these changes, once I click on the refresh pivot table or refresh all from data tab nothing changes on the pivot tables.
Thanks
Satya

Power Query/Data Management Gateway data refresh not working

Pretty new to o365/Power BI, but here's what I've got going on (hopefully someone can help me out):
I created a data management gateway and data source. The data source says it's online in the PowerBI admin center, and it seems to be working correctly. I can open Excel 2013 on my desktop (logging in as my trial o365 account which has Power
BI associated with it) and connect to the data source via Power Query using the oData option. I make sure to import the data into the model, and then open up the PowerPivot window and create a simple pivot table using the data in the model.
that all works just great. The problem comes when I upload the workbook and try to update it. I've tried a few different ways.
1. When I try to manually refresh the workbook by opening it in my o365 site and going to data-->refresh I get the following error:
      An error occurred while working on the Data Model in the workbook. Please try again.
      We were unable to refresh one or more data connections in this workbook.
      The following connections failed to refresh:
      Connection: Power Query - dbo_DimProductCategory
      Error: Out of line object 'DataSource', referring to ID(s) 'a75593f3-c34d-4f83-9458-49aa2cece164', has been specified but has not been used.
      The following system error occurred: Class not registered
      The provider 'Microsoft.Mashup.OleDb.1' is not registered.
      Power Query - dbo_DimProductCategory
2. When I go into Power BI and go to "Schedule Data Refresh" for the workbook, I get the following error:
      Sorry, the data connections in this report arenâ€™t supported for Scheduled Refresh.
      Technical Details â–¼
      Correlation ID: B3CE4B10-2137-E593-6FCF-189B73465190
      Date and Time: 03/31/2014 06:20:39 PM (UTC)
Any help would be greatly appreciated. If you need additional information, I'd be happy to provide it.

Hey Guy,
Thanks for the reply.
The "data source type" of the data source in Power BI is "SQL Server" (there was only that and Oracle available to select from)
The "data source type" that Power Query is using in Excel is "From oData Feed"....which is using the Power BI data source....which is using the data management gateway.
A few follow up questions if you have a second
1. Do you know when PowerQuery data refresh will be supported? (just a general idea....weeks, months, next year?)
2. Is there any other way to connect to (and be able to refresh) PowerBI data sources referencing "on prem" data via the data management gateway? I tried using the oData feed URL in non-PowerQuery areas of excel (excel data tab, PowerPivot directly)
but it didn't work. If there's some other way to connect to and refresh on prem data, i'm all ears :D
Really appreciate your help, thanks for taking the time.

Power Query; How do I reference a Power Pivot table from a Power Query query

Hi,
It's pretty awesome how you can define Extract Transform and Load processes within Power Query without having to type in a single line of code. However how do I reference a Power Pivot table from a Power Query query to avoid me repeatedly accessing
the same data source (CSV) file with a view to increasing performance?
We are aware of the reference sub menu option with Power Query. However the new query created by the "reference" option still seems to refresh data from the data source (CSV) rather than just referencing the base query. Is this understanding
correct? There does seem to be a lot of hard disk activity when re-running the new query which is based on a base query rather than a data source. So we were hoping the new query would just need to reference the base query in memory rather than rescanning
the hard disk. Is there any way to ensure that the reference query just rescans the base query in memory?
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Hi Kieran,
This sounds like something to be suggested for a future release. At the present time, Power Query will always re-run the entire Power Query query when refreshed. The Reference feature is analogous to a SQL view whereby the underlying query is always re-executed
when it's queried, or in this case refreshed. Even something like using the Power Query cache to minimise the amount of data re-read from the disk would be helpful for performance but the cache is only used for the preview data and stored locally.
It would be a good idea to suggest this feature to the Power BI team via the feedback smiley face.
Regards,
Michael Amadi
Please use the 'Mark as answer' link to mark a post that answers your question. If you find a reply helpful, please remember to vote it as helpful :)
Website: http://www.nimblelearn.com, Twitter:
@nimblelearn
Hi Michael,
Glad to hear from you about this. And thanks to Kieran for bringing a very good valid point to debate. Will be glad to see this in future release.
- please mark correct answers

Refresh Pivot Bug in Power Query version 2.16.3822.242

Similar Messages

Maybe you are looking for