{"id":26508,"date":"2021-01-20T11:26:17","date_gmt":"2021-01-20T11:26:17","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=26508"},"modified":"2021-03-06T09:08:51","modified_gmt":"2021-03-06T09:08:51","slug":"what-is-popupservice-in-powerapps-component-framework","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2021\/01\/what-is-popupservice-in-powerapps-component-framework\/","title":{"rendered":"What is PopupService in PowerApps Component Framework?"},"content":{"rendered":"

Introduction<\/h2>\n

While creating PCF control, we have mostly encountered difficulties to create popups and dialog boxes. We use external UI libraries like Fluent UI that enables us to manage popups in our PCF control.<\/p>\n

Have you heard of PopupService in PowerApps Component Framework?<\/p>\n

Let us find out what the PopupService is.<\/p>\n

PopupService is a native PCF option that we can use to manage popups in the PCF control.<\/p>\n

Sometimes you may design PCF control wherein your control does not require including Fluent UI or any other external library for popups. In this situation, you can go with native PopupService option to create popups.<\/p>\n

PopupService includes seven methods to interact with the popups including createPopup, closePopup, deletePopup, openPopup, updatePopup, getPopupsId and setPopupsId. To know more about these methods, follow the link here<\/a>.<\/p>\n

Prerequisites<\/h2>\n

\u2022 Microsoft PowerApps CLI must be installed.
\n\u2022 Should be familiar in creating basic field control.<\/p>\n

Below are the steps to create a PCF control, which includes a button. By clicking this button our custom popup will open.<\/p>\n

1. In index.ts file, create three global variables in class which will include a container to append the button in it, PopUpService which will give us the methods discussed in the introduction of this blog and isUpdateViewCalled to restrict extra updateView() call with default value as false.<\/p>\n

\"1PopupService<\/a><\/p>\n

2. Initialize the container in init() method of PCF.<\/p>\n

\"2PopupService<\/a><\/p>\n

3. In updateView() method we are going to create a button on click of which a popup will appear. At first, we will check the condition of this._isUpdateViewCalled to call the updateView method only once and not multiple times. Further, we will create four variables for our html container, button element, popup content and a close button.<\/p>\n

\"PopupService<\/a><\/p>\n

4. After this variable declaration in updateView() method, create and append button element to the htmlContainer. Let the name of button be \u2018Quick View\u2019, by clicking which it will call popUpClick() that will open the popup. As shown below we also added a class name \u2018button\u2019 to give some style to our button.<\/p>\n

\"4PopupService<\/a><\/p>\n

Css:<\/p>\n

\"PopupService<\/a><\/p>\n

To add CSS in your PCF control, create a .css file and add your css in it. To use that file, add it in the resources part in ControlManifest.Input.xml file as shown below:<\/p>\n

\"PopupService<\/a><\/p>\n

5. Now it is time to create the content for the popup. After creating and appending \u2018Quick View\u2019 button to htmlContainer, add logic to create the content, which can be either a HTML or a plain text. For the demo purpose, we will show primary contact record detail of the account on which our control is present. We will retrieve the record using webApi.retrieveMultipleRecords function and in success callback function, we will create the popup content and set true to isUpdateViewCalled for not calling it again.<\/p>\n

In content, we will create a HTML table in which we will show three field values – Name, Email address and Phone number of primary contact. You can choose any field you want along with the table; we will add a button to close the popup on click of which we will call the close Popup method.<\/p>\n

So, first we will create fetchXML query and retrieve the record.<\/p>\n

\"PopupService<\/a><\/p>\n

Further will create the popup content in the success callback function.<\/p>\n

\"PopupService<\/a><\/p>\n

We also added \u201ccontainer\u201d css class to the popUpContent and \u201ccloseButton\u201d class to the button on the popup. In addition, we added some styling to the table and its content.<\/p>\n

Css:<\/p>\n

\"PopupService<\/a><\/p>\n

6. Now it is time to create our popup Object. Before creating it we need to make an interface the above class. While creating the interface, extend it to ComponentFramework.FactoryApi.Popup.Popup. Now we can use this interface as a definition type for our popup object.<\/p>\n

\"PopupService<\/a><\/p>\n

Will create the Popup Object below our html content, in which we will add popup properties like,
\ncloseOnOutsideClick: Indicates whether popup will close with an outside mouse click. When set to false, the popup will not close with an outside mouse click.
\ncontent: Static DOM element to be inserted of type HTMLElement.
\nname: Unique name of Popup.
\ntype: The type of popup, which is described in the enum PopupType. Root: 1 and Nested: 2<\/p>\n

\"PopupService<\/a><\/p>\n

The createPopup(popUpOptions) method will create our popup.<\/p>\n

7. After configuring our control on a field in the form, the button will look as shown in the below image:<\/p>\n

\"PopupService<\/a><\/p>\n

On click of the above button, we will call our popUpClick() in which we are calling openPopup(popUpName) method, that will open the popup created in the above step.<\/p>\n

\"PopupService<\/a><\/p>\n

Now you can see the popup as shown in the below image with details of Primary contact in it.<\/p>\n

\"PopupService<\/a><\/p>\n

We can see the three fields with their values and a close button. On click of \u2018Close\u2019 button, we will call closeCustomPopUp() in which we will call closePopup(popUpName) to close our custom popup.<\/p>\n

Below is the complete code for the above Popup.<\/p>\n

CSS:
\n.container {
\nwidth: 400px;
\nheight: 200px;
\nbackground-color: azure;
\nposition: absolute;
\ntop: 50%;
\nleft: 50%;
\ntransform: translate(-50%, -50%);
\nborder: 1px solid slategray;
\npadding: 10px;
\nborder-radius: 10px;
\n}<\/p>\n

.button {
\nborder: 1px solid #333;
\nborder-radius: 5px;
\nbackground-color: #EFEFEF;
\nwidth: 100%;
\npadding: 10px;
\n}<\/p>\n

.closeButton {
\nwidth: 100%;
\nborder: 1px solid black;
\nmargin-top: 10px;
\nbackground: azure;
\npadding: 10px;
\n}<\/p>\n

table {
\nwidth: 100%;
\nbackground: #EFEFEF;
\nborder: 1px solid #333333;
\ncolor: black;
\n}<\/p>\n

td {
\npadding: 10px;
\n}<\/p>\n

Code:
\nIndex.ts (TypeScript)
\nimport { IInputs, IOutputs } from “.\/generated\/ManifestTypes”;
\ninterface PopUpInterface extends ComponentFramework.FactoryApi.Popup.Popup {
\npopupProp: object;
\n}
\nexport class CustomPopUp implements ComponentFramework.StandardControl<IInputs, IOutputs> {
\nprivate _container: HTMLDivElement;
\nprivate _popUpService: ComponentFramework.FactoryApi.Popup.PopupService;
\nprivate _isUpdateViewCalled: boolean = false;
\n\/**
\n* Empty constructor.
\n*\/
\nconstructor() { }<\/p>\n

\/**
\n* Used to initialize the control instance. Controls can kick off remote server calls and other initialization actions here.
\n* Data-set values are not initialized here, use updateView.
\n* @param context The entire property bag available to control via Context Object; It contains values as set up by the customizer mapped to property names defined in the manifest, as well as utility functions.
\n* @param notifyOutputChanged A callback method to alert the framework that the control has new outputs ready to be retrieved asynchronously.
\n* @param state A piece of data that persists in one session for a single user. Can be set at any point in a controls life cycle by calling ‘setControlState’ in the Mode interface.
\n* @param container If a control is marked control-type=’standard’, it will receive an empty div element within which it can render its content.
\n*\/
\npublic init(context: ComponentFramework.Context<IInputs>, notifyOutputChanged: () => void, state: ComponentFramework.Dictionary, container: HTMLDivElement) {
\nthis._container = container;
\n}
\npublic popUpClick = () => {
\nthis._popUpService.openPopup(“CustomPopUp”);
\n}<\/p>\n

public closeCustomPopUp = () => {
\nthis._popUpService.closePopup(“CustomPopUp”);
\n}
\n\/**
\n* Called when any value in the property bag has changed. This includes field values, data-sets, global values such as container height and width, offline status, control metadata values such as label, visible, etc.
\n* @param context The entire property bag available to control via Context Object; It contains values as set up by the customizer mapped to names defined in the manifest, as well as utility functions
\n*\/
\npublic updateView(context: ComponentFramework.Context<IInputs>): void {
\nif (!this._isUpdateViewCalled) {
\nlet htmlContainer: HTMLDivElement;
\nlet quickViewButton: HTMLButtonElement;
\nlet popUpContent: HTMLDivElement;
\nlet closeButton: HTMLButtonElement;<\/p>\n

\/\/============ content of our popup =============
\nhtmlContainer = document.createElement(‘div’);
\n\/\/button to show our popup
\nquickViewButton = document.createElement(‘button’);
\nquickViewButton.innerHTML = “Quick View”;
\nquickViewButton.classList.add(‘button’);
\nquickViewButton.onclick = () => this.popUpClick();
\nhtmlContainer.appendChild(quickViewButton);
\n\/\/@ts-ignore
\nlet page = context.page;
\nlet entityId = page.entityId;
\nlet fetchXml = “<fetch version=’1.0′ output-format=’xml-platform’ mapping=’logical’ distinct=’false’>” +
\n“<entity name=’account’>” +
\n“<attribute name=’name’ \/>” +
\n“<attribute name=’primarycontactid’ \/>” +
\n“<attribute name=’telephone1′ \/>” +
\n“<attribute name=’accountid’ \/>” +
\n“<order attribute=’name’ descending=’false’ \/>” +
\n“<filter type=’and’>” +
\n“<condition attribute=’accountid’ operator=’eq’ value='{” + entityId + “}’ \/>” +
\n“<\/filter>” +
\n“<link-entity name=’contact’ from=’contactid’ to=’primarycontactid’ visible=’false’ link-type=’outer’>” +
\n“<attribute name=’emailaddress1′ \/>” +
\n“<attribute name=’telephone1′ \/>” +
\n“<\/link-entity>” +
\n“<\/entity>” +
\n“<\/fetch>”;
\nlet fetchQuery = “?fetchXml=” + encodeURIComponent(fetchXml);
\ncontext.webAPI.retrieveMultipleRecords(page.entityTypeName, fetchQuery).then((record: any) => {
\n\/\/take the value in record variable
\nrecord = record.entities[0];
\nthis._isUpdateViewCalled = true;
\npopUpContent = document.createElement(‘div’);
\npopUpContent.innerHTML = “<table>” +
\n“<tr>” +
\n“<td>Primary Contact: ” + record[“_primarycontactid_value@OData.Community.Display.V1.FormattedValue”] + ” <\/td>” +
\n“<\/tr>” +
\n“<tr>” +
\n“<td>Email: ” + record[“contact1.emailaddress1″] + ” <\/td>” +
\n“<\/tr>” +
\n“<tr>” +
\n“<td>Telephone: ” + record[“contact1.telephone1″] + ” <\/td>” +
\n“<\/tr>” +
\n“<\/table>”;
\npopUpContent.classList.add(“container”);
\ncloseButton = document.createElement(‘button’);
\ncloseButton.innerHTML = “Close”;
\ncloseButton.classList.add(‘closeButton’);
\ncloseButton.onclick = () => this.closeCustomPopUp();
\npopUpContent.appendChild(closeButton);<\/p>\n

\/\/ Popup object
\nlet popUpOptions: PopUpInterface = {
\ncloseOnOutsideClick: false,
\ncontent: popUpContent,
\nname: ‘CustomPopUp’, \/\/ unique popup name
\ntype: 1, \/\/ Root popup
\npopupProp: {}
\n};
\nthis._popUpService = context.factory.getPopupService();
\nthis._popUpService.createPopup(popUpOptions);<\/p>\n

});
\nthis._container.appendChild(htmlContainer);
\n}
\n}<\/p>\n

\/**
\n* It is called by the framework prior to a control receiving new data.
\n* @returns an object based on nomenclature defined in manifest, expecting object[s] for property marked as \u201cbound\u201d or \u201coutput\u201d
\n*\/
\npublic getOutputs(): IOutputs {
\nreturn {};
\n}<\/p>\n

\/**
\n* Called when the control is to be removed from the DOM tree. Controls should use this call for cleanup.
\n* i.e. cancelling any pending remote calls, removing listeners, etc.
\n*\/
\npublic destroy(): void {
\n\/\/ Add code to cleanup control if necessary
\n}
\n}<\/p>\n

Conclusion<\/h2>\n

As illustrated above, you can now add popups in PCF control using PopupService.<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction While creating PCF control, we have mostly encountered difficulties to create popups and dialog boxes. We use external UI libraries like Fluent UI that enables us to manage popups in our PCF control. Have you heard of PopupService in PowerApps Component Framework? Let us find out what the PopupService is. PopupService is a native\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,19,44,1929,1985],"tags":[545,592,2129,2130],"class_list":["post-26508","post","type-post","status-publish","format-standard","hentry","category-dynamics-365","category-dynamics-crm","category-power-apps","category-pcf","category-power-automate","tag-dynamics-365-crm","tag-dynamics-crm","tag-popupservice-in-powerapps","tag-powerapps-component-framework"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/26508","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=26508"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/26508\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=26508"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=26508"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=26508"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}