PL 400: Identify and resolve connector and API errors(Manage and troubleshoot apps)

Data works as fuel in the business world. Connector provides the bridge between data source and power apps and power platform. Connector is core component of power platform. A connector may provide table of data or action. A connector can provide a table of data or action. However, Microsoft offers over 300 different connectors, it also allows creating custom connectors for communication between different apps. All connectors sit on a hosting environment that is owned by Microsoft.

As we know a connector is a wrapper or proxy around an API that interacts between power automate or power apps and back end service or data source. It allows a bi-directional communication and can access data form both cloud and on premises servers.

Custom Connector Architecture:



We have already discuss design the custom connector. for the more update, please click this link. Here we will discuss about connector and API errors and their resolutions.

HttpRequest- Failure : Server returned: 500 Internal server Error:

HTTP status code 500 is a common error response, indicating that the server encountered an unexpected unexpected condition that prevented it from fulfilling the request.

Resolution:

There can be several reasons for what might be causing this issue, but the most common reason is related to how the path and host fields are defined in the swagger. The path of each action is relative to the host of the API you're trying to reach, which ends up getting constructed as <host/path>.


Service Timeout:

Service timeout is also a common error that occurs when the server takes so long to respond. Possible reasons could be server issues, outdated browser, cache, sporadic internet connection and others.

Resolution:

Generally we try to connect again the service.

InvokerConnectionOverrideFailed error:

If we get an error similar to '{"error":{"code":"InvokerConnectionOverrideFailed","message":"Could not find any valid connection for connection reference name 'shared_office365' in APIM tokens header."}}'. Try these:

Resolution:

  • Clear the browser's cache.
  • Delete the connection and then re-add it.


The reply url specified in the request does not match the reply urls configured for this application.

This is configuration issue when we create new custom connector

Resolution:

To resolve this error, we need to add Redirect URL generated by custom connector in App registration Reply URL’s.

Comments

Post a Comment

Popular posts from this blog

Powering Up Your Analytics: Exploring Power Query in Power BI

Image
Data is a valuable asset that has a profound impact on almost every aspect of modern life. Its proper collection, analysis and application can promote innovation, improve efficiency and solve complex challenges in various sectors. In data processing, ETL is a comprehensive process that includes data extraction, transformation, and loading, while Power Query is a specific tool that facilitates the "extract" and "transformation" aspects of ETL, allowing data to be collected and analyzed. Permission is granted to process. And reporting. is ready. It becomes easy to do this. Microsoft's ecosystem of products. Power Query is a data transformation and data preparation engine. Power Query is available in Microsoft Excel and Power BI. Power Query provides a user-friendly and intuitive interface for data professionals and analysts to access and manipulate data from various sources without the need for extensive coding or scripting. It allows users to connect to a wide ra
Read more

Power App Component Overview : Canvas App vs Model-Driven App

Image
The Power Platform is a suite of low-code/No-code tools and technologies developed by Microsoft and Power App is integral component of Power Platform. Power App is platform that enables users to build custom web and mobile applications with a visual interface and minimal coding. The platform support various data sources, including Microsoft 365, Azure Service, and many other, enabling users to integrate and interact with their existing data and systems. In Microsoft's Power Apps, there are two main types of apps that we can create: Canvas Apps: Canvas apps provide a blank canvas where you can design highly customizable applications with a drag-and-drop interface.  Model-Driven Apps: Model-driven apps are built on top of the Dataverse, which provides a set of pre-built data entities and business logic. There are few key technical difference between Canvas App and Model Driven App: During the usability analysis, these high-level technical differences need to be considered. The choi
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more