PL 400: troubleshoot app issues by using Monitor and other browser-based debugging tools(Manage and troubleshoot apps)

In the world of information technology, bugs are referred to as errors, defects, defects or gaps in expected software behavior. Generally, the developer team strives to develop error-free applications, but there are many reasons, which generate bugs such as incorrect analysis, communication gaps, lack of proper testing activities and others. As we know, customer satisfaction is of utmost importance for any organization and only bug free products can keep the customer happy.

According to Wikipedia:
In computer programming and software development, debugging is the process of finding and resolving bugs within computer programs, software, or systems


Pixel perfect canvas apps provide amazing user interface for specific task or business requirement. With the simplicity of canvas apps, users can easily develop apps by drag and drop. In such platforms, troubleshooting or bug fixing is a big challenge but canvas apps provide many features (out of the box) and methods for such activities.

View Results:

Canvas apps operate by creating functions such as filter and sort to create powerful formulas. The result of the formulas is always associated or interwired with the controls. This feature helps us to go through the middle of the formula and understand what is happening and what is the result.

Monitor:

A monitor is a tool that gives makers the ability to view a stream of events from a user's session to diagnose and troubleshoot problems. It supports both the apps (canvas and model driven apps) with limited support.



For Canvas Apps:

  • Data connectors/network events(error , status codes)
  • Screen load metrics
  • cross screen dependency warning
  • User actions( navigate, select, set property and others)
  • Custom trace.
  • Delegated vs non-delegated queries
  • verbose switch (Internal telemetry)

For Model Driven Apps:

  • Form load sequence
  • Pert metrics
  • XHR Sync vs Async
  • Form Rules
Monitor doesn't support the scenarios in the following tables :
  • Monitor connected to apps running on a mobile device (native players) : Canvas App
  • Monitor connected to a canvas app embedded in a model driven app or custom page : Canvas App
  • Monitor connected to a SharePoint custom from app: Canvas App
  • Monitor connected to a MS Team embedded app : Canvas App
  • Monitor isn't supported on Internet Explorer version 11 : Canvas and Model Driven App
Trace Function:

Trace is a function to follow the execution path and display the activities of a specific canvas app or diagnostic information related to the app. Trace can be enabled in the development environment as well as in the production environment. This information can help you check for errors or unwanted results while the Canvas App is processing a request/response. The Trace function can be used to provide additional information that can be viewed in the Power Apps Monitor tool along with real time diagnostic information for the app for debugging or other app activities to help identify problems.

Syntax:
Trace(Message, Trace_severity, Custom_record)

Message: Required. The information to be traced.
Trace_severity: Optional. The severity level of the trace record in App insight.
Custom_record: Optional. A record containing custom data that will be recorded in Application Insights.

Comments

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more