PL 400 : Configure a PCF component manifest (Create a Power Apps Component Framework (PCF) component)

The Microsoft Power Apps Components Framework enables us to create reusable code components that can be used with our Power Apps applications. This framework empowers professional developers to build code components when out-of-the-box components do not fit the needs of app makers. These components are metadata driven, performant and can be configured and used on both canvas and model-driven applications.


Code components consist of three elements:

  1. Manifest
  2. Component implementation
  3. Resources
Power Apps components are meta driven.


Power App component framework enables professional developers from within and outside Microsoft to develop custom code components as reusable visual extension. These components are configured by manifest.

Manifest is xml document that describe:
  • Component Name.
  • The type of data that can be configured, either a field or a dataset.
  • Any properties that can be configured in the application when the component is added.
  • A list of resource files that the component requires.

 

<?xml version="1.0" encoding="utf-8" ?>
<manifest>

<control namespace="TestNameSpace" constructor="JSTestControl" version="1.0.0" display-name-key="JS_TestControl_Display_Key" description-key="JS_TestControl_Desc_Key" control-type="standard">

<property name="TestFirstProperty" display-name-key="TestFirstProperty_Display_Key" description-key="TestFirstProperty_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" />
<resources>
<code path="JS_TestControl.js" order="1" />
<css path="css/JS_TestControl.css" order="1" />
</resources>
</control>
</manifest>




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