In this video, learn to enable Power Apps Application Monitoring with Azure Application Insights. The following topics are covered in this video: ( 0:00 ) - Intro ( 0:36 ) - What is Azure Application Insights ( 1:32 ) - The timesheet app ( 2:12 ) - Creating an Application Insight for the timesheet application ( 3:55 ) - Identify and copy the application instrumentation key ( 4:09 ) - Enabling the timesheet application with the instrumentation key ( 5:32 ) - Working with Application Insights ( 8:06 ) - Outro For additional information on Azure Application Insights, please follow these resources: Microsoft Docs - What is Azure Application Insights? here Adam Marczak - Azure for Everyone: Azure Application Insights Tutorial, here To check out my YouTube channel visit: https://youtube.com/user/mgomezb1 LIKE AND SUBSCRIBE!!! Until next post! MG.- Mariano Gomez, MVP
A lot of the guiding principles for deploying Named Printers in a Terminal Server or Citrix environment comes from two of my favorite articles, written by my good friend and fellow Microsoft Business Applications MVP, David Musgrave (twitter: @winthropdc ). David happens to be the creator of Named Printers and probably understands the product better than anyone I know. You can read his articles here: Using Named Printers with Terminal Server Using Named Printers with Terminal Server Revisited These articles continue to be very relevant if you are in an environment where a Print (or Printer) server is the norm and published printers are standard. Print servers are used to interface printers with devices in a network, but mostly to standardize administrative policies, and balance the document load that printers can manage. Part of the standardization is to ensure printers are uniquely identified across the networks, regardless of whether you are accessing the network remotely or ph
The Integration Manager parameter file, Microsoft.Dynamics.GP.IntegrationManager.ini , provides a few keys that allow the application to perform certain actions according to the values and the sections in which these parameters are initialize . Here is a list of keys for the initialization file per section within the file: IMBaseProvider section This section controls the overall behavior of the Integration Manager application. AutoUpgradeIntegrations= 0/1 Prompts IM to check whether to upgrade an integration or not. CommandTimeout=30 Time allotted to execute a particular IM operation. If the operation is not successful in the time alloted, the record integration will fail. HideMsgBox= False/True Hides IM registration window during the application launch. UseOptimizedFiltering= False/True Allows you to maintain the same sorting as the original source. One note that I would make is that the following switch was put in more for performance. If you notice that your data is not coming in th
Comments