New Idea

Yesterday, all my datasets were refreshing just fine but today nothing happens.

- The automatic refresh hasn't done anything.

- When I press "Refresh now", I get a "popup" saying "preparing refresh" for a split second and then nothing happens.

 

The only way to update the data is to refresh the Desktop version and then upload it. 

 

I have datasets connection to an on-premises database and one connecting to a sharepoint site.

- The on-premises connection usually works perfect, but now nothing happens.

- The sharepoint connection usually brings up an error,  if I try to refresh, but now nothing happens (I just tried it this time as a test, as it usually doesn't work automatically).

 

Can you please help troublefinding - It seems like an issue on you online portal somehow.

 

Thanks in advance.

 

// Tommy

Status: Delivered

Invalid Credentials on Scheduled Refresh

Status: Accepted
by paulopaim Frequent Visitor on ‎11-21-2016 05:05 AM

I'm having the problem below, I've put the credentials again, but the error continues.

 

powerbierror.PNG

Status: Accepted

Search Box on Slicer Missing

Status: Accepted
by MikeThibs Regular Visitor on ‎01-05-2017 04:39 PM

Hello,

     The Search Box on the Slicer Visualization seems to have a bug when a PBIX file is loaded to the Power BI Service. This issue is affecting the drop-down format of a Slicer. Also it seems to only affect Slicers with a larger amount of items. When there are 2 or 3 items in the slicer the search box will appear however if there are 20 plus or more items it is not working. I've tried several different browsers, so I don't believe that is the issue. Below are screenshot showing the search box has been enabled and the missing search box when you select the drop down. Please help!!! We're on the verge of rolling out hundreds of new Power BI accounts and this is a serious issue when you have large slicer needs.

 Search On.jpgSearch Not Showing.jpg

 

 

Status: Accepted

errorJPG.JPG

I'm getting this error since yesterday on a new dataset. It is a simple excel file table. I've done the following.

Signed out of Power BI Desktop and back in

Got the latest personal gateway

turned the gateway service off / on

republished multiple times during this process.

 

Others seem to be having the same issue. see thread here

There is a current support site error message, but it is specific to SharePoint as a data source only.

Status: Accepted

I though this was fixed in the last release and seemed to stopped happening after I downloaded the newest version. Now it is back and is a complete pain to deal with. Please fix this issue. Sign in issue_Ink_LI.jpg

 

 

 

 

Status: Needs Info

Dashboard sharing Disabled for non-PRO users ?

Status: Delivered
by djnww Established Member ‎04-27-2017 05:28 AM - edited ‎04-27-2017 05:34 AM

We can no longer share a dashboard with users from our own workspace. I received the message:

"This dashboard contains Power BI Pro content. Only users that have Power BI Pro will have access to it"

 

I confirmed my fears by publishing the simplest of reports which is 100% non-pro content. There have been a few other mentions of it on the forum in the past couple of hours, but I thought I'd create an official post. 

 

1st sharing was disabled from Group Workspaces to non-pro users. Surely Microsoft has accidentally disabled ALL sharing for non-pro users ? If not, you can imagine the uproar.

 

Is anybody else facing the same problem ? 

 

Power BI clearly states that we are able to share personal dashboards with non-pro users. 

Error.PNG

 

 

Status: Delivered

Invalid credentials on Sharepoint folder

Status: Accepted
by csabil Frequent Visitor on ‎11-22-2016 10:46 PM

Since yesterday I'm having an issue connecting to an excel file in a Sharepoint folder. It was already working, but I made some changes and republished it. Refresh works fine in Power BI Desktop, but online. It seem it's trying to connect to a Sharepoint list, instead of folder. I have an other report connecting to an other excel file in the same folder and it works fine. Could this be connected to the issue in North Europe? I'm in that datacenter.

 

Capture.PNG

Status: Accepted

In the new January, 2017 release, I get a "Report has already been published" error message when I try to use the PUBLISH option to Update a report that exists on the Service from Desktop.

 

- Steps:

--I updated a report in Desktop that had been previously published to the Service.

--I selected the PUBLISH menu option in Desktop

--I selected MY WORKSPACE (where the report was located)

--I received an error "Report has already been published" and the update failed.

 

I've tried with several different reports both with the Service running and with the Service not running.  I've also exited Desktop and restarted it and repeated the operation.  In all cases, I got the same error.

Status: Delivered

Bug in "Don't include in Report Refresh"

Status: Delivered
by ImkeF Super Contributor on ‎01-10-2017 07:58 AM

There's a bug in "Don't include in report refresh" like described here: http://community.powerbi.com/t5/Desktop/Disabling-quot-Include-in-Report-Refresh-quot-works/m-p/1017...

unfortunately I didn't test correctly and this thread is closed, but the bug is still there and preventing solutions for problems like this:

http://community.powerbi.com/t5/Desktop/Big-file-needs-no-update/m-p/111341#U111341

 

If the query that shall not be refreshed is not referenced by any other query or part of a UNION-operation in DAX, then everything works fine, but if it is referenced as mentioned, then it will be loaded again.

A lot of the usecases for this features are of this kind, so this bugfix is really needed !!!

Status: Delivered

We are trying to use Power BI to pull data from SAP BW leveraging both BEx queries and cube connections. With each scenario we are running into different issues and were trying to figure out if this is a Power BI Limitation/Issue with 1. Connecting to a Warehouse 2. They way that Power BI is communicating with SAP BW to pull its data or is this a SAP BW Limitation/Issue based on how SAP BW servers up data.

 

Tested With Cube:

0FIGL_C10 -General Ledger (New) Transaction Figures

 

Data Load is very slow

Adding new columns and refreshing data seems to take a very long time. I don't know if this is a sap warehouse issue, an OLAP issue, or a power bi Issue. I had our basis team monitor our BW environment when connecting to a cube where I selected all the columns. The cube contains 349,628 records which is based on generating the SQL Statement from the cube (In SAP BW RSA1) and executing that in SQL Server Management Studio. This call eventually failed with the following ‘RFC_ABAP_RUNTIME_FAILURE: TSV_TNEW_PAGE_ALLOC_FAILED which I was told was due to running out of memory. Prior to testing this I had Basis increase our memory footprint on the server in an attempt to rule out memory issues.

 

Column limitation (selecting to many columns) or possibly and combination of Columns + Rows

When I connect to a cube and select 1-4 fields everything is pretty responsive. But as you start adding more and more fields the performance starts to suffer. In testing it looks like we can add 12 fields without any issue (Super Slow Refresh Times) but once we hit the 13th field we get an RFC_ABAP_RUNTIME_FAILURE – TIME_OUT.

 

MDX

I don’t write a lot of MDX statements so my statement could be the cause of the issue but I run into the same issues remain. Which makes sense because I believe Power BI is connecting to SAP BW through the BW Open Analysis Interface OLBAP BAPIs regarless of if you going againt a Cube, BEx Query, or MDX.

 

This works:

Select   NON EMPTY [Measures].MEMBERS ON COLUMNS,   NON EMPTY   [0FISCYEAR].Members *   [0CO_AREA].Members *   [0COMP_CODE].[LEVEL01].Members   PROPERTIES     [0COMP_CODE].[20COMP_CODE]   on rows   from [$0FIGL_C10]   WHERE ([0COMP_CODE].[1100], [0FISCYEAR].[K12016])

 

Doesn’t Work

Select   NON EMPTY [Measures].MEMBERS ON COLUMNS,   NON EMPTY   [0FISCYEAR].Members *   [0CO_AREA].Members *   [0COSTCENTER].Members *   [0CHRT_ACCTS].Members *   [0CO_AREA].Members *   [0CURTYPE].Members *   [0FUNC_AREA].Members *   [0GL_ACCOUNT].Members *   [0PROFIT_CTR].Members *   [0SEGMENT].Members *   [0VALUATION].Members *   [0VERSION].Members *   [0FISCPER].Members *   [0FISCPER3].Members *   [0FISCVARNT].Members *   [0FISCYEAR].Members *   [0COMP_CODE].[LEVEL01].Members   PROPERTIES     [0COMP_CODE].[20COMP_CODE]   on rows   from [$0FIGL_C10]   WHERE ([0COMP_CODE].[1100], [0FISCYEAR].[K12016])

 

Key and Text Values

The last think I want to touch on is the key values. Power BI does not appear to give you the ability to select or toggle between the text and key values. Though MDX I was able to include the properties section and include the key value (Which was nice) but this should be standard functionality.

 

Tableau

I wanted to try and cover all my bases and rule out as much as I could to try and pin point the issue. As such I used Tableau to connect to the same structure as it’s my understanding that it also utilizing the BW Open Analysis Interface OLBAP BAPIs to query SAP BW. I’ll point out that I don’t really use Tableau but it was a tool that was available to use a test. Once again I had Basis monitor the SAP Environment to help track down any issues. Within seconds tableau had pulled in the Metadata and I was able to create a sheet. Tableau appears to provide a live query connection to the cube whereas Power BI appears to try and load the data first which may also be contributing to the performance issues. Again I just wanted to test with another tool to try and rule out the SAP environment.

 

 

 

With SAP being our ERP system we need the ability to effectively be able to query our data warehouse and provide the user community with self-service reporting/analytics. With the issues listed above its making this a very difficult process to move forward with. Any ideas or suggestions would be greatly appreciated. We love Power BI and the users who have seen our demos love what it can do and I feel like we are always installing this on someone’s machine.

 

Thoughts?

Hi all,

 

I have a client who is on the latest release of Power Bi Desktop (v 2.46.4732.721), although this issue also occurs on the previous version (2.46.4732.581). When they create a new measure on top of a live tabular model connection and set the formatting, the formatting only persists for that Power BI Desktop session. When they save the file and close and reopen, the formatting reverts back to the default, which is especially unreadable for percentages and currency. Is this fixable? Thanks!

Status: Accepted

All of the sudden (perhaps after the April 2017 update?), any dashboards we share out-of-tenant from Power BI Web are missing the tabs along the bottom to switch between the different reports in that dashboard.  

We tested with in-tenant sharing and it works fine - only an issue when shared externally.   

 

We tried creating a new dashboard from scratch with 2 simple tabs and published out of tenant - same issue.  All tabs are just gone!  

 

 

By the way, I did see a similar thread (http://community.powerbi.com/t5/Issues/Report-tabs-missing-on-shared-dashboard/idi-p/150884) but it seems too different from what we're experiencing.  In that case, 3 out of 5 tabs disappeared and it happened when shared internally or externally.  Our issue happens only when sharing externally.  Perhaps the same issue.

 

We noticed a warning on the client side that only appears when looking at it out-of-tenant - this may be related to what's happening or perhaps not:

/13.0.1700.1783/scripts/ai.0.js:1 AI: USRACT_StringValueTooLong message:"string value is too long. It has been truncated to 1024 characters." props:"{value:Error: [$injector:unpr]

http://errors.angularjs.org/1.5.9/$injector/unpr?p0=%24templateCacheProvider%20%3C-%20%24templateCac... at

https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:25... at

https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:62... at Object.d [as get]

(https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:60... at

https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:62... at d

(https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:60... at e

(https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:60... at Object.invoke

(https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.dependencies.externals.bundle.min.js:60... at https://app.powerbi.com/13.0.1700.1783/scripts/powerbiportal.depen}"

u.warnToConsole @ /13.0.1700.1783/scripts/ai.0.js:1

There seems to be other issues with PBI of late (data failed to load when first opening a dashboard) so perhaps the tabs missing are part of a bigger problem.  However, for now that is the problem that is getting in the way of us delivering analytics to our clients.

 

Any help would be greatly appreciated!

 

 

-Caleb

 

P.S. We had another issue with out-of-tenant dashboards where the Export Data just didn't work for them.  It was eventually fixed, but I'm beginning to wonder whether or not out-of-tenant sharing is the red-headed-stepchild of the PBI feature set.  It could certainly use a little more testing with each release...while I love the pace of innovation of PBI this isn't the first time that something in this dark, scary corner of PBI was broken and our clients were impacted.  Food for thought if this post happens to cross into any PBI QA LOS.

 

Status: Delivered

 

Power BI Desktop Version: 2.42.4611.701 64-bit (January 2017) Installed today.

 

Login window blocked by "Working on it" spinner popup after Power BI Desktop idle in background for a bit. I didn't nail down the time but both times it was over 20 minutes. The login expires after an indeterminate amount of time of inactivity, over 20 minutes at least. Clicking publish brings up the login window but is behind the "Working on it..." popup.

I have to end the task, open Power BI, click login up in the top right corner, then I can publish.

 

screen shot of issue

 

 

 

Status: Delivered

Unable to cast object of type 'ComDataConvert' to type 'ComDataConvert'. The exception was raised by the IDataReader interface. The sync works perfectly on power bi desktop. Any help in this would be greatly appreciated.

Export to Powerpoint

Status: Accepted
by jlilleystone Visitor on ‎03-03-2017 01:46 AM

We like to use the Export to Powerpoint feature but I think we've found a bug. If I publish a report from PBI desktop to the PBI.com service and then export the report to Powerpoint it works fine. If in the PBI.com service I take a copy of that report to modify it (by using Save As and giving it a different filename) the export to Powerpoint produces blank slides for each page in the report. The report has no embedded images and only has 5 or 6 pages in the report. Please help - being able to export consistently to Powerpoint is a big part of our use of PBI. If it doesnt work we may have to stop using it. Of course we can take screen grabs of each page and paste them into Powerpoint but I wouldnt expect my users to have to resort to that approach. Thanks.

Status: Accepted

We utilize out-of-tenant shared dashboards extensively and are aware of the change made yesterday to the Power BI Free service.  We've had our clients activate their free Pro trial and are using a Pro account to share out-of-tenant.

 

However, even after activation, out-of-tenant shared dashboard links are not working.  They just display the Power BI logo and it blinks continuously.  

 

I tried going to the dashboard as the owner (again, logged into a Pro account), clicking "Stop Sharing" on the dashboard and re-sharing with the client (who had activated the Pro trial) and still, they see the blinking Power BI logo.

 

Using developer tools in the browser, I see a failed XMLHttpRequest:

URL: https://wabi-us-north-central-redirect.analysis.windows.net/powerbi/invitation/dashboards/invitation...
Method: HTTPS POST

Error code: 401 (Unauthorized)

 

Looks like yesterday's switch-over broke out-of-tenant dashboards.  This seems to happen all the time, out-of-tenant sharing is very unstable and doesn't seem to be tested well enough when changes are made to the Power BI Service.  I've opened many other tickets reflecting these issues on this site.

Please let me know if you need any more details, all of our clients are dead in the water right now (even after activating the Pro trial).  @v-haibl-msft - you've been very helpful in the past on keeping me informed & updated on issues like this so wanted to proactively make you aware what's happening here.

 

Regards,

Caleb Blanton

Status: Accepted

Not sure if this is related to the data refresh issue, but starting yesterday I have two different external customers (both in California) that view different dashboards.  They are able to get to the dashboard frames, however get an error stating that "something went wrong.. unable to load the data model".

 

Anyone else experienceing this with external users?

 

Our data is on prem, we use the personal gateway, and the external customers are using the link provided in the original MSFT email I shared with them.

 

Thanks,

 

Status: Needs Info

We have a production implementation of Power BI for which we turned on device based Conditional Access (CA), and added relevant AD groups. After turning on CA, users in the device based AD group are unable to sign in from Power BI desktop and also cannot sign in upon installation of a new Enterprise Gateway.

We get the following message: Unable to sign in. Sorry we encountered an error while trying to sign you in. Details: AADSTS50000. Device platform Unknown used by the user is an unsupported device platform. Supported device platforms are iOS, Android, and Windows flavors.

We are on a Windows platform and tested from Windows 8 and Windows 7 machines, and encountered the same error on both. This issue applies to October 2016 and September 2016 versions of desktop. To prove that CA triggered this issue, we used a test user not in the device based AD group. The test user was able to sign in successfully.

This issue is critical as it prevents us from being able to publish directly from Power BI desktop and prevents users from installing a new Enterprise Gateway.

Please let me know if you need any additional information. If you need Trace ID, Correlation ID or Timestamp, I can provide it via email.

Status: Investigating

Publish Error from PowerBI Desktop

Status: Accepted
by pbillava Frequent Visitor on ‎05-10-2017 04:27 AM

HI,

After latest update of PowerBI. There is error when I click on Publish from PowerBI Desktop

Error.png

Status: Accepted
Idea Statuses