{"id":37028,"date":"2024-01-11T13:02:46","date_gmt":"2024-01-11T07:32:46","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=37028"},"modified":"2024-01-15T17:26:02","modified_gmt":"2024-01-15T11:56:02","slug":"how-to-directly-access-custom-action-from-custom-pages-in-power-apps","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2024\/01\/how-to-directly-access-custom-action-from-custom-pages-in-power-apps\/","title":{"rendered":"How to directly access Custom Action from Custom Pages in Power Apps"},"content":{"rendered":"

Power Apps offers versatile design experiences, including model-driven apps<\/a> and Canvas apps<\/a>, and the recent addition of Custom Pages. Based on the client’s recent requirements, we had to replace the OOB Opportunity entity with the custom one. In response to our client’s specific requirements, we meticulously recreated essential functionalities, such as the “Opportunity Close as Won” and “Close as Lost” processes. Notably, these functionalities were expertly crafted using Custom Pages to introduce a streamlined and tailored user interface, effectively replacing the default popups. So for the agenda of this blog, we will focus on how we used the Custom action in the Custom page to recreate the Opportunity close functionality in the custom Opportunity Entity.<\/p>\n

\"Custom<\/p>\n

Step 1:<\/strong><\/p>\n

As we know, once the Opportunity is closed, one new record gets created in the Opportunity close Entity regarding that record, and the status of the Opportunity record gets changed. All these things can be done with the help of the custom action.<\/p>\n

To call the Custom action On the Custom page, we have to enable one setting and make sure this is enabled.<\/p>\n

1. Go to settings.<\/p>\n

2. Go to Upcoming features.<\/p>\n

3. Enable access to Microsoft Dataverse Actions.<\/p>\n

\"Custom<\/p>\n

This feature is available in the previously created apps. For newly created apps, this feature has been automatically enabled ever since the general availability of this feature. Even if you are not able to access the custom action on the custom page, then do the below list of actions.<\/p>\n

1. Go to settings<\/p>\n

2. Go to Upcoming features.<\/p>\n

3. Go to the retired section.<\/p>\n

4. Make sure this feature, \u2018Disable access to Microsoft Dataverse actions, is disabled, as seen below in the highlighted part.<\/p>\n

\"Custom<\/p>\n

Note \u2013 Please do not get confused by seeing the retired setting. Refer to the given links for more information that indicates general availability: https:\/\/learn.microsoft.com\/en-us\/power-apps\/maker\/canvas-apps\/connections\/connection-common-data-service#call-dataverse-actions-directly-in-power-fx<\/a> and https:\/\/powerapps.microsoft.com\/en-us\/blog\/direct-power-fx-dataverse-action-invocation-ga\/<\/a><\/p>\n

Step 2:<\/strong><\/p>\n

After this, you have to add the Environment entity and all the entities that you require on the Custom page.<\/p>\n

\"Custom<\/p>\n

Step 3:<\/strong><\/p>\n

In the process of enhancing the Custom Opportunity Entity with a Close Opportunity Modal using Custom Pages in Power Apps, it becomes imperative to set default values for specific fields on the Custom Page. This task is accomplished through Power FX formulas.<\/p>\n

Step 4: <\/strong><\/p>\n

The final step involves invoking a custom action upon clicking the ‘OK’ button. This process utilizes the Environment table to access and execute actions available within the CRM environment. The following steps provide a formal guide for calling the custom action and configuring inputs based on the specific requirements.<\/p>\n

1. Input parameters are defined in the action, as seen below.<\/p>\n

\"Custom<\/p>\n

2. Set the values for the variables as shown below.<\/p>\n

\"Custom<\/p>\n

3. Identify and select the custom action from the available actions within the Environment table (in our case, it is e8s_Create_ClosedOpportunity). This action is responsible for closing the Opportunity and creating a record in the Opportunity Close Entity.<\/p>\n

4. Referencing the provided image, add inputs to the selected custom action. This step involves configuring the inputs required for the action to operate successfully.<\/p>\n

\"CustomStep 5:<\/strong><\/p>\n

It’s crucial to handle the output parameter from the custom action. Specifically, we aim to retrieve the ‘Opportunity Close’ record’s ID generated upon closing the opportunity. This information is then used to determine whether the action was successful, closing the Custom Page accordingly, or displaying an error message if the record creation fails. Within the custom action configuration, ensure that the ‘Opportunity Close’ record ID is specified as an output parameter.<\/p>\n

Conclusion<\/strong><\/h2>\n

This blog explained the process of invoking a custom action from Power Apps to close opportunities and create related records, emphasizing the importance of handling output parameters for a successful user experience. Overall, the guide showcased the flexibility of Power Apps in creating tailored solutions for efficient business processes.<\/p>\n

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

Power Apps offers versatile design experiences, including model-driven apps and Canvas apps, and the recent addition of Custom Pages. Based on the client’s recent requirements, we had to replace the OOB Opportunity entity with the custom one. In response to our client’s specific requirements, we meticulously recreated essential functionalities, such as the “Opportunity Close as\u2026 Read More: How to directly access Custom Action from Custom Pages in\u2026 »<\/a><\/span><\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[44],"tags":[1337],"class_list":["post-37028","post","type-post","status-publish","format-standard","hentry","category-power-apps","tag-power-apps"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t