I have a web service connection (Qaaws connection) in my dashboard built using Xcelsius/Dashboards 4.1 that is set to refresh and filter on our business units.
It is behaving differently every time I attempt to refresh the connection. Sometimes when it is refreshed and told to filter the data does not change. Other times when refreshed it just deletes the data from the dashboard. And eventually, after multiple refresh attempts, it will bring the correct data.
I have been watching the web traffic using fiddler and can see what is happening, but cannot explain why it will not refresh correctly and pull the correct data on the first attempt to refresh the connection.
Any help that can be provided would be greatly appreciated.
In fiddler I can see that the correct prompt (Key Due Date) is being sent. I can also see the output in fiddler that is the same as what shows in the dashboard.
When the data does not change in the dashboard the fiddler output shows me the data that shows up when no filter is placed on the connection.
When the data is deleted I see this repeated about 4 times as the output in fiddler
As for running the same patch level of xcelsius on the server I pretty sure I am, but need to check to make sure.
I have not considered BI services instead of Web service query (Qaaws) connections at the moment. All of the other connections in the dashboard are built using Qaaws and are behaving normally. Just having an issue with a particular connection.
The way we are pulling data is we have WeBi reports built and web services published off of these reports. Normally I would like to schedule the webi and have the dashboard pull the lastest instance, but due to the particular prompts with certain reports I cannot schedule them without having to re-running them every morning when i get in.
Could be versioning of software, could be a bug, could be a corrupt connection.
You’ve tried deleting it and setting it up again?
How many connections do you have?
I mentioned BI services, only becuase I understand that they are more performant than QAAWs.
I have tried deleting the connection and recreating it again multiple times. I have even gone back and deleted the published web service and published it again in Webi Rich Client.
I have a total of 17 connections in this dashboard. It is a very complex dashboard at the moment. We are attempting to rebuild it using the Qaaws connection.
Dashboard was previously built using LiveOffice connections, but we are moving away from using these.
Have not been able to find any specific issues out there that resemble what is happening with this connection on any SAP website.
I believe I misspoke earlier. I currently am running the connection as a BI Service, publishing a webi report block as a web service. The connection type that I am using in Xcelsius is Web Service Query (Query as a Web Service).
Could that be the issue? Should I be using a different connection type in Xcelsius? Maybe the Web Service Connection type?
I have never been able to see any difference between Web Service Query and Web Service Query (Query as a Web Service). I’m sure there is one, but they’ve always functioned exactly the same for me.
A couple basic questions:
Are there other connections that are refreshing at the same time?
Do you have other blocks published from that same WebI document?
There are other connections refreshing at the same time when I am running the dashboard.
But as a test, I set up a separate refresh button that only refreshes this specific connection…so i can see results faster and not refresh the entire dashboard each time. This behavior can be seen when refreshing this connection by itself and when I am refreshing the entire dashboard.
And yes there are two blocks in this webi that are published. Would having multiple blocks of data published off of a single webi cause issues?
Yes, it does. And, unfortunately, it’s terribly inconsistent. We had a number of dashboards just suddenly start crashing one day because of this issue. SAP told us it was our fault for publishing multiple blocks from the same report.
The basic problem, as far as I can tell, is that the cache gets confused when the same user is pulling multiple copies of the report with different prompt values. So splitting up your source data as much as possible is recommended.
Seriously. And I have searched. There is no documentation anywhere that indicates that it is not best practice. Not in the official documentation, not in any white paper or note on their site, and not that I’ve found in any book on the topic. It’s a super-secret best practice.
(BOB member since 2005-01-06)
!