PL 400 : create a definition for the API (Create custom connectors)

API gives the advantage of communication between two software products or applications. In the past, there was a challenge between the two applications especially in cross platform. API is an acronym for Application Programming Interface, which acts as an intermediary that allows two applications to talk to each other. APIs allow different platforms, applications and systems to communicate and share information with each other.

API means Application Programming Interface.


In a power platform, the connector is the key component that helps to connect different types of platforms to the power platform. There are over 350 connectors available in the Power Platform that help talk to Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. It provides users with a way to link their accounts and leverage a set of pre-built actions and triggers to build their apps and workflows.
A connector is a proxy or a wrapper around an API.

According to Microsoft:
A custom connector is a wrapper around a REST API (Logic Apps also supports SOAP APIs) that allows Logic Apps, Power Automate, or Power Apps to communicate with that REST or SOAP API.

Sure, a custom connector works as a communication point to talk to all kinds of platforms, applications, and more, but it needs to define a set of protocols, standards, and methods. There are many ways to receive and respond to requests, so a custom connector defines an API that helps to understand how the communication interacts. This definition can be separated with two categories; Technical specification that describes the data exchange options between solutions with a specification made as a request for processing and data delivery protocols. The other API specification is; Which defines standardized data exchange between web services.

After  API Authentication, we need to define the API definition, so that Logic Apps, Power Automate, or Power Apps can communicate with API. The following approaches are supported:

  • An OpenAPI definition (formerly known as a Swagger file)
  • A Postman collection
  • Start from scratch using the custom connector portal ( Power Automate and Power Apps only)



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