I try to run a flow in Power Automate but I receive this error message:
This is contrary to the admin data policy, which restricts the use of the <Shared_dataflows> connector
Could you help ?
Related
im getting a error to refresh mi report in Power BI Service. Currently I can refresh the report locally however when I publish the report and then want to sync it to a gateway I get the following error:
I have this configuration in the new data source:
Finally i have this configuration in ODBC ( 64x):
Sometimes i get error of credentials but its impossible because y refresh the data with these credentials locally.
Thanks!
I try using different gateways, changue the configuration of the ODBC and Power BI Report. I have synchronized another report with the same gateway and it works correctly. Now when I try to link a second report to this same gateway I get the error.
My problem is very easy: I'm retrieving all stocks about lithium on the ASX market from this web page.
I created a Power BI dashboard that you can visualize here.
As the source is Web I would like to refresh it every day using the Gateway connection, so I have successfully installed it on my computer that I turn on every day:
The problem is that instead of a successful daily refresh I have a daily error:
Failed to test the connection to your data source. Please retry your credentials.
Some credentials aren't validated as they are set to skip test connection.
If I enter in the Edit credentials I see the error:
Failed to update data source credentials: The credentials provided for the Web source are invalid. (Source at https://www.marketindex.com.au/commodities/lithium.)Show details
This because I'm using Authentication method: Anonymous and Privacy level setting for this data source: Public. But this is exactly what I'm using on Power BI desktop and it's working!
What am I doing wrong here?
Why the same connection is working fine on Power BI Desktop but not the same dashboard uploaded online?
EDIT: the On-premises data gateway looks installed without problems
It seems like the issues you're experiencing may be caused by the link you're using (https://www.marketindex.com.au/commodities/lithium), although I'm not sure exactly why.
For example, as has been mentioned in the Do I Need a Gateway for Web post, one can use Web.Contents instead of Web.BrowserContents in the raw M code in the Power Query Editor to avoid using a gateway. However, when I test this implementation using the link that you provide, I get an error when refreshing from Power BI online.
If I test this implementation using an HTML table from the https://tradingeconomics.com/commodity/lithium website, though, and set the data source credentials as follows, then I am able to successfully refresh the dataset from Power BI online.
I tested this with another HTML table from a random webpage and an online refresh worked as well. So it seems like there is something odd about how Power BI online interacts with the Market Index website and this is causing your issue. Potentially because of some authentication configuration on the Market Index side of things? I'm not able to help with looking further into why this is occurring, though.
Would you be able to use a different website with similar information as a data source for your report? If so, you could avoid the issues you're experiencing and avoid using a gateway in general if you wanted.
If you go this route, it seems like using the included "Scheduled refresh" setup in Power BI online works, but I will include the Power Automate scheduled refresh setup below in case this is desired instead.
Power Automate Scheduled Refresh
One can use Power Automate to "schedule" dataset refreshes instead of the included "Scheduled refresh" functionality in Power BI online. The steps are a little too long to include here, but the Refresh your Power BI dataset using Microsoft Flow article outlines the process on setting this up. There are various triggers that you can use to trigger your flow. The linked article uses one that triggers based on a SharePoint action, but there is a Recurrence trigger that can be used to trigger your flow at regular intervals/times.
Just set up your flow, make sure that it is "turned on", and your dataset will refresh at regular intervals from the cloud.
I got the read access on a dataset in bug query. However when I try to connect it in data studio. I get a configuration error.
Tried reconnecting the dataset and even though i can access the dataset if i login in BigQuery.
Any ideas, if I need any special permissions to connect that dataset to from datastudio?
If you get configuration error on any shared dataset make sure you have Viewer Permission. BigQuery Viewer Permission will not work for this.
I'm trying to get data from one of the reports available in the google play console. Specifically the user_acquisition report. I set up the data transfer service within the google cloud platform in order to use the BigQuery API.
When querying that specific report the results are partial. Some columns match the results I get when downloading the report manually but other columns just have the value null although the downloaded report shows that there should be numerical values there.
Another peculiar thing is that when specifying a date range for the query (month of may for example) the result will show about 1/3 of the dates in that month but there should be a row for each day of the month.
When looking at the transfer runs history, some of the runs have completed successfully, and some have failed giving the error message: Error code 5 : No files found for any reports. Please make sure you selected the correct Google Cloud Storage bucket and Google Play reports exist. But if no files are found, then how am i getting any results at all?
The users of both the GCP and Google Play Console are the owners of the project, so there shouldn't be any issue with the permissions to access the bucket where the reports are stored.
I tried creating another data transfer service to see if it can even find the reports. It did find some of the files but not the one I'm interested in. The transfer run history shows the same error as mentioned above.
Has anyone had some similar problem before and perhaps can offer some sort of solution? Or maybe just has some insights into why this problem is occurring?
I think the issue could be related with the availability of the desired report, since I've found that only some reports are supported by this service:
Detailed reports (Reviews, Financial reports)
Aggregated reports (Statistics, User acquisition)
Could it happen that the specific report your want to export is not supported?
If that's not the case I think you should file a support case sharing the "Resource name" into the Transfer details of the failed exports (and correct ones for reference). Alternatively of the support ticket you can also report a defect on the transfer service on a Public Issue tracker. The support team can help you to review further the error message.
Within Power BI (On cloud) console, the datasets screen is showng errors in form of alert icon, in detail the error for all of them is :
Something went wrong
Unable to connect to the data source undefined.
Please try again later or contact support. If you contact support, please provide these details.
Underlying error code: -2147467259 Table: <TABLE_NAME>.
Underlying error message: AnalysisServices: The following system error occurred:
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.DataSourceKind: AnalysisServices
Microsoft.Data.Mashup.ValueError.DataSourcePath: <path1>;<path2>
Microsoft.Data.Mashup.ValueError.Reason: DataSource.Error
Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net
Activity ID: 259c4fc7-dde9-449b-b108-9498b001ea25
Request ID: 56d4ee25-b539-4c05-8cd4-24b894507475
Time: 2019-06-13 12:12:51Z
I already reviewed gateway/ Analysis services but seems to be OK, Any idea what additional to review?
You may check the different privacy level settings in Power BI Desktop and Power BI Service. Make sure you have the same privacy level security.
Check Power BI gateway logs. For example, I received the same error message. Log information showed connectivity issue to SQL. I checked the server, and named pipes was disabled in client protocols. Since the report data source was configured by server name, connectivity could not work. Enabling it resolved the issue.