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

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

Is Debt Prosperity or Trap?

 “What can be added to the happiness of a man who is in health, out of debt, and has a clear conscience?”  Adam Smith Grandfather Bhishma lay on the bed of arrows and was preaching the future king of Hastinapur about political science, economics and the duties of the king. He took a deep breath and told Yudhishthira " Fire, debt and enemies must be dealt with quickly and completely. If there is any balance left, they can continue to grow. " The future king was listening with curiosity and was eager to learn about the complete knowledge from his grandsire. Each moment was important as the sun was moving from south to north. Either we read the quote of the father of modern economics or both ancient great scholars are advising to avoid debt. But the whole of modern economics is based on the debt that advises the public to borrow money. The aggressive campaign of banks and financial institutions has been luring more and more loans. Even democratic governments and public banks con
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