I want to refresh a reporting widget, either triggered by cube data update (server side) or triggered periodically (probably on the client side).
It's possible to refresh a full report (only available on Enterprise Real time).
There is a setting available in Configuration / Layout / Refresh Period field (advanced). This will ping the server each x seconds and if new date refresh the report accordingly.
hope it helps.
Related
I have created a CDS connection in PowerApp platform under particular environment which I can see in list there as follows:
But when I go to PowerApp admin portal and try to use these connection to create a ConnectionSet then only single connection appears there, which is of Dynamics 365 for Operation. I don't see any other connection to choose from to proceed with integration task. My intention is to integrate the CDS data from associated Dynamics 365 for Talent to Dynamics 365 for Operation.
Screenshot of ConnectionSet creation step with only available connection:
Please let me know what I have missing and hence the other connection not appearing in list.
To tell if a connection can be used by Data Integration, please try the instructions below.
Log on to https://admin.powerapps.com/environments using Chrome
Enable network trace (F12) for the browser, and switch to [Network] tab
Type [integratorApp] in the filter editor box
Power Apps Admin Portal
Click [Data integration] to switch to Data Integration page
In the network trace tab, look for [targetTypes] and in the [Preview] tab, observe a list of supported types and their corresponding apiId’s.
For [Common data service], the type is [CDS2] and apiId [/providers/Microsoft.PowerApps/apis/shared_commondataservice]
Supported Target types
In the [Network] tab, type [powerApps] in the filter edit box
Click on [+New connection set] to open [Connection Set] dialog
In the [Network] tab, look for [connections?api-version…]. There might be more than one calls if you have multiple PowerApps environment.
Switch to [Preview] in the response, observer connections that have apiID’s matching what are supported, and check if the connection in question is listed.
Connections
I have a speech project which uses web service. I have set the timeout for 45 seconds in OD but when I deploy it, I get the following error for the first calling user in EP log viewer:
Fetch time out when opening timed stream for url =
http://example.com/AppName/SetLanguage?___DDSESSIONID=EF3397385F3E9BC0E89D526B3FCB811A%3A%2FAppName.
Timeout was = 15000
Session=ccmpp03-2018026140450-10
I think, EP has some default timeout of 15 sec.
1)Is there a way to increase it?
2)Is there any other solutions for this problem?
You should check this:
How to change the default Avaya Voice Browser (AVB) timeout value from an Avaya Voice Portal system?
you can change fetch time in AEP that is for all the application configured in AEP. if you want to change the fetch time for single speech application you need to add a property in the root then configured the fetch time for individual speech application.
enter image description here
enter image description here
I am profiling some MS SQL queries with the SQL Server Profiler for my C# Application that I develop with Visual Studio and IIS Express:
The duration that is given for the event "Audit Logout" (16876 ms) is the total time between login and logout. The duration for the query is only 60 ms.
Login/Logout events are related to the setting up / tearing down.
From What is "Audit Logout" in SQL Server Profiler?
I would like to understand the time difference of 16816 ms (= 16876 ms - 60ms) in more detail.
a) Is it possible to log more events (like a "debug mode")?
b) Is it right to assume that the time difference is only due to tearing down because the end time of the "Audit Login" event is the same as the start time of the query execution?
c) Is there some other tool for analyzing (setup and) tear down times?
d) Does the time difference depend on my query? With other words: would an optimization of the query also help to reduce that time difference?
What I observed so far for #DevTime is that it makes a difference if I start my application the first time (IIS Express is started by Visual Studio, the database is created using the entity framework, example data is written to the database) or if I start it the second time when the database already exists.
For a login after the first start the time difference is about 15 s larger than for a login after the second start. The query that is marked in the example above is executed after user login. Therefore I would expect that the initialization of the database already has been finished at that time and that the initialization would not have any effect on the time difference. Nevertheless it seems to have an influence.
Some related articles:
What is "Audit Logout" in SQL Server Profiler?
Fixing slow initial load for IIS
SQL Server audit logout creates huge number of reads
https://learn.microsoft.com/de-de/sql/relational-databases/event-classes/audit-logout-event-class
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/84ecfe9e-ff0e-4fc5-962b-cffdcbc619ee/audit-logout-event-seems-slow-on-occasion?forum=sqldatabaseengine
When starting the SQL Profiler a window Trace Properties is shown.
The second tab Events Selection is the place where the considered events can be selected.
Activate the option Show all events.
Enable for example the option "Showplan XML FOR Query Compile" under the section "Performance" to log more events.
Also see How to determine what is compiling in SQL Server
I dont have a solution with your recomandations, please the database continue whit problem. all the querys are so good in the process time, only the logout audit constantly show a long time duration. the network its laso good. I think that this logout time affected the efficiency
I’m trying to run a Dataset to build a KPI on SSRS 2016 Enterprise addition but, it give me the hereunder message although it run fine on the Report Builder:
[An Error has occurred.
The data set could not be processed .
There was a problem getting data from the Report server Web Services.]
I already changed the Dataset Timeout to Zero and the Database Query Time out to Zero on the RsReportServer.config
When I limit the Dataset to one row (a shorter query) it run fine which, mean the issue could be in the Web service or session timeout.
Setting Time-out Values for Report and Shared Dataset Processing (SSRS)
You can Reporting Services specify time-out values to set limits on
how system resources are used. Report server supports two time-out
values: An embedded dataset query time-out value is the number of
seconds that the report server waits for a response from the
database. This value is defined in a report.
A shared dataset query time-out value is the number of seconds that
the report server waits for a response from the database. This value
is part of the shared dataset definition and can be changed when you
manage the shared dataset on the report server.
A report execution time-out value is the maximum number of seconds
that report processing can continue before it is stopped. This value
is defined at the system level. You can vary this setting for
individual reports.
Most time-out errors occur during query
processing. If you are encountering time-out errors, try increasing
the query time-out value. Make sure to adjust the report execution
time-out value so that it is larger than the query time-out. The time
period should be sufficient to complete both query and report
processing.
https://learn.microsoft.com/en-us/sql/reporting-services/report-server/setting-time-out-values-for-report-and-shared-dataset-processing-ssrs
The response from Google glass location property is very fast. Is it controlable? What is the control point for Google glass location
You can't control the frequency of the location callback event. In my experience if the user is moving around it may fire every few minutes. If the user does not have their phone paired or on IOS has killed the MyGlass app; then you will not get location data as there will be no GPS info. If you want more control over frequency of updates you need to build a GDK component and launch it as a service on Glass.
When you are subscribed to location updates on the Mirror API, you will receive location updates at least every 10 minutes, assuming GPS from a paired phone is available.
This 'at least 10 minutes' usually translates to almost exactly every 10 minutes. However, if there is another service on your Glass device that is making more frequent use of location services, such as a background service that pulls the GPS, location updates may be sent by the Mirror API more frequently.
You don't have the ability to specify location data update frequency. It is expected that you will get location updates about once every 10 minutes (but maybe more).