I am trying to invoke a report using rest V2 API but I have a problem regarding the dataSource concurrency access. I will just provide the following scenario where application 1 requested the report then application 2 requested the same report.
Application 1 :
Retrieve the version of report 1
Patch the data source of the report 1 with dataSource1
Sleep 10 seconds
Download the report 1
Application 2 :
Retrieve the version of report 1
Patch the data source of the report 1 with dataSource2
Download the report 2
Because the application 1 pauses 10 seconds, application 2 patched the report with data source 2 and the result of this is that application 1 gets the results that are provided by the dataSource 2.
I want any suggestion to solve this issue.
Thanks in advance
Related
I am using Azure Logic App workflows to refresh a Power BI dataset every 5 minutes. The workflow was working for several weeks without any issues . But since last 2 days the dataset refresh is failing (Message - Another refresh running at same time). I have attached the picture on the refresh status. Though it shows the alternate refresh status as Success , the Power BI dashboard shows the same number all the time.
Is there a way to fix this the steps I tried - Disabled and enabled the flow, Deleted the flow and created again but its the same problem.
Also there are other reports that do not have this issue. I am using a Service account for the API connection .Is there a way to check if there is another refresh running at same time. Thanks for any inputs.
.
We are building a reporting solution using Power BI. We have OLPT data source. It is aggregated and loaded into a data mart. Power BI dashboards will source data from data mart in aggregated format.
Now the requirement is that, there should be download icon on the Power BI dashboard. On clicking the download icon the transactional data should be exported to CSV instead of aggregated data.
Example:
OLTP Data:
Order_No Qty Status
1 10 Delivered
2 8 Pending
3 5 Failed
4 3 Delivered
Aggregated data (in Datamart):
Status Order_Count
Delivered 2
Failed 1
Pending 1
When the download icon clicked, the following data should be exported to CSV and downloaded in users local system.
Order_No Qty Status
1 10 Delivered
2 8 Pending
3 5 Failed
4 3 Delivered
I have a dataset for 3 days I can not update it on Power BI service, knowing that on DESKTOP it is normally updated in 30 minutes. the dataset is powered from a SQL server database, via a data gateway. the data gateway is well updated. the incremental update is activated and the dataset retrieves only the data of the last 3 days to each update.
Here is the generated error message :
Data source error: The XML for Analysis request timed out before it was completed. Timeout value: 17998 sec.
Cluster URI: WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 680ec1d7-edea-4d7c-b87e-859ad2dee192
Application ID: fcde3b0f-874b-9321-6ee4-e506b0782dac
Time: 2020-12-24 19:03:30Z
What is the solution to this problem please.
Thank you
What license are you using?
Without premium capacity, the max dataset size can be 1GB. Maybe your dataset size has crossed this mark? If you are using the shared capacity, then you can check the workspace utilized storage size by clicking on ellipses at top right corner. Then click on storage to see how much is utilized for that workspace.
Also note that in shared capacity there is a 10GB uncompressed dataset limit at the gateway (but this should not be an issue as you have only 3 day data in refesh)
Also check whether your power query query is foldable (on the final step you should be able to see the 'show native query' option). If not then incremental refresh does not work and results in querying the entire data.
Also, note that 17998 sec means 5 hours. What is your internet speed?
Test Environment:
CPU: Intel Core i5 7th Gen (2.71GHz - 4 Logical Processors)
RAM: 12 GB (Free 6 GB)
HDD: 1 TB (Free 700 GB for SQL and NAV)
NAV: 7.0.33781 (2013)
SQL: 2008 SP1
OS: Windows 10 Pro
Note: This is the System where both SQL and NAV system are running together for test purposes. This happens in Live server environment also.
Problem:
Inside the NAV RTC, every page related to Item Table (with no customization) take too much time to load the records. This includes Drill-down pages, Assist Edit Pages and List Pages. This does not happen when navigating through single records (ie: Next and Previous actions) on Item Card page.
Observation:
When loading above said slow-down pages, the CPU performance monitor indicates about 90% usage taken by MSSQLSERVER itself.
Experiments:
- Taken out the Item Table (TableID: 27) to a fresh DB (Demo DB of NAV)
and works like a charm since less data.
- Imported Item table and related pages from a fresh DB (Demo) to this
issue causing DB but nothing went okay.
- SQL SELECT * FROM query with no filters and with all the columns
loads within 0.1 seconds of execution time.
Extra Specifications:
Item Master has 18000 Records in total with no customized fields or newly created fields/flowfields. Neither no codes on Pages' OnOpen triggers nor in table code.
I was faced with a very strange behavior of Data Service Server (v. 3.5.0).
I prepared quite simple service with some resources for MS SQL Server RDBMS data source. When I call one of resources with simple select query I get answer after 6 seconds (six seconds).
The same select in MS SQL Server Management Studio returns data after 15-100 ms.
The same select in WSO2 DSS Database Explorer returns data after max 15 ms.
The same select in Netbeans returns data after max 100 ms.
I tried JSTL and Microsoft drivers. The result is the same.
Everywhere except DSS service I get answer in max. 100 milliseconds. Result of these queries is very small - 6-8 rows with about 10 columns.
Which is the reason for such behavior?
Could somebody help me?
The reason is very, very strange.
I tried a simple query like:
SELECT a1,a2 .... FROM someView WHERE a1=:parameter
When parameter is of type STRING (I think, like parameter for PreparedStatement) query returns results in about 4000 milliseconds (???).
If parameter is of type QUERY_STRING query returns results in 10 milliseconds (!!!!). Result is very small - about 10 rows with 5 columns.
Time was measured by net.sf.log4jdbc.DriverSpy, but the same difference I get with pure Microsoft Jdbc and Jtds drivers.
Why such a big difference? 400 times faster?
One question remained: What is to blame:
WSO2 DSS software?
JDBC driver?
SQL Server?