Hi @christianirgens ,
Could some detailed information be provided:
For example, is there a corresponding error message about this error?
Can you provide some screenshots of the problem? Please be careful not to include sensitive information.
Best regards.
Community Support Team_Caitlyn
Hi @wilsonchen
I created a slicer with single-select in PBI Desktop . Then I published the report to Service , selection has not changed in any way and remains the same as before the publish. My Desktop version is 2.121.644.0 64-bit (September 2023) . Maybe you can update Desktop to the latest version and test it again!
Best Regards,
Community Support Team _ Ailsa Tao
Hi @chang_B
It’s a known issue . The engineers are actively working on this issue and I will come back with an update if there is any progress.
Best Regards,
Community Support Team _ Ailsa Tao
Hi @BRNS
It sounds like you are trying to refresh a Power BI dataset that includes a calculated table that depends on another table that uses Direct Query mode to connect to an Analysis Services data source. Unfortunately, Power BI does not currently support refreshing datasets that include calculated tables that depend on tables using Direct Query mode.
One solution you could consider is to change the source data for the calculated table so that it does not use Direct Query mode. This would allow you to refresh the dataset, but you would need to find a way to incorporate the data from the Direct Query source into the calculated table using other means, such as using Power Query to merge or append the data.
Another option is to use a separate dataset for the calculated table, and then use a measure or a report-level filter to control the data displayed in the report based on the data in the calculated table. This would allow you to refresh the main dataset without affecting the calculated table.
It's also worth noting that Power BI recently introduced the ability to refresh datasets that include calculated columns, so you may want to consider using calculated columns instead of a calculated table if that meets your needs.
Best Regards,
Community Support Team _ Ailsa Tao
Hi @gp10 ,
We've found feedback from other users who have had similar experiences to yours. Here are some suggestions from the PG team Please see if this mitigates your problem.
"Customer appears to be using Feb 2023 version of the gateway. Can you please ask the customer to upgrade gateway to the latest version and re-capture gateway logs? There were some changes in the token refresh implementation in Jan 2023, upgrading will assure we have the latest version being used. Also ensure only one version of the gateway is installed.
Customer should also consider removing all existing credentials to the dataflow and recreating them. Sometimes that can fix authentication problems in PBI service."
Best regards.
Community Support Team_ Caitlyn
Hi @sgrewal
Power BI Desktop has no login restrictions for external tenants. The only restriction is when it comes to sharing. Internal users are not allowed to share content directly from within the organization to external users, and there is no distinction between inside and outside the organization when logging into PBI Desktop or PBI Service. Unless your company's network security guidelines restrict the use of other domains.
I was able to log in to PBI Desktop using the two accounts in the screenshot, obviously they are not part of the same organization.
Best Regards,
Community Support Team _ Ailsa Tao
Hi @venuswang
The issue has been fixed. Please have a check.
Best Regards,
Community Support Team _ Ailsa Tao
Hi @ospinozza
I can see the Dataflows Gen2 in filters , so Item Type has the category Dataflow Gen 2. If you can't see it in the list, is there a possibility that you filtered out Dataflow Gen 2?
Best Regards,
Community Support Team _ Ailsa Tao
Hi @msg88 ,
We've seen feedback from users in another thread with similar experiences to yours, and my colleagues are investigating this issue in full force. I will give you feedback here if there is any progress.
As a temporary workaround, you can roll back to the previous version first.
Best regards.
Community Support Team_ Caitlyn
Hi @TiCordeiro
This issue has been submitted to ICM , the ID is 343344031 . If there is any progress, I will come back to update .
Best Regards,
Community Support Team _ Ailsa Tao
Existing ICM for similar issue(ICM 297756751). It should be a new known issue that dataflow refresh taking long times that usual to complete. Employee engages this issue as well.
Hi @SanilMaru
PG is working on fixing this issue. Should be 3 - 4 weeks for the fix to be in production . Please wait patiently .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @hugo-gomes
Issue is mitigated in all regions except CANADA central. ETA for Canada is 19th .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @sgrewal @ricardcom ,
Glad the problem was disappear, then I will close the thread.
Best regards,
Community Support Team_yanjiang
Currently it have been considered as a known issue which would be fixed in early of September, so please stay tuned.
Best Regards,
Community Support Team _ Yingjie Li
Hi @lysdexia
Can you describe your procedure in detail ?
Best Regards,
Community Support Team _ Ailsa Tao
Hi all,
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_Caitlyn
Hi @AHeyman_
When did this happen? default values and current value no matter which one is selected, the final exported data is default values? Did you apply RLS in your report ?
Best Regards,
Community Support Team _ Ailsa Tao