{"id":39587,"date":"2024-10-30T16:18:29","date_gmt":"2024-10-30T10:48:29","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=39587"},"modified":"2024-10-30T16:26:44","modified_gmt":"2024-10-30T10:56:44","slug":"formload-to-formloaded-enhancing-form-functionality-with-formloaded-in-power-apps","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2024\/10\/formload-to-formloaded-enhancing-form-functionality-with-formloaded-in-power-apps\/","title":{"rendered":"FormLoad to FormLoaded: Enhancing Form Functionality with formLoaded in Power Apps"},"content":{"rendered":"

\"Enhancing<\/p>\n

As developers, we understand that effective form handling is important for delivering a good user experience. Traditionally, many of us depend on \u201cformLoad\u201d,<\/strong> but this approach has significant drawbacks, such as inconsistent loading data and insufficient feedback<\/strong> during asynchronous data fetching, which can lead to user frustration.<\/p>\n

In many projects, the formLoaded<\/strong> method has proven to be incredibly useful. It makes sure that every part of the form is completely loaded<\/strong> before users can start using it, which improves both reliability and performance. Research shows that using addOnLoad<\/strong> can create challenges with completing tasks afterward, especially when trying to set up data right as the form loads.<\/p>\n

Let’s say John is working on an Employee Management System where he manages employee information. He ran into a scenario where he needed to load all employee data through an API when the form opens and initialize a field called “Salary.”<\/strong> Afterward, he needed to perform an additional step to calculate the “Monthly Tax.”<\/strong><\/p>\n

\"Enhancing<\/p>\n

While working on this, John ran into two main issues:<\/p>\n

    \n
  1. Data Retrieval Time:<\/strong> With over 20,000 employee records, pulling <\/strong>in all the data<\/strong> took a long time<\/strong>. The “Salary” field didn\u2019t get filled until all the data was loaded, causing delays<\/strong>.<\/li>\n
  2. Timing for Tax Calculation:<\/strong> During the form load, he couldn\u2019t get the salary details quickly enough for the tax calculation step. The initial setup<\/strong> took about 5.23 seconds<\/strong>, and by the time it finished, the tax calculation process had already started, leading to empty or missing values<\/strong> for the salary.<\/li>\n<\/ol>\n

    \"Enhancing<\/p>\n

    In trying to achieve this scenario, John also used the addOnLoad <\/strong>method, but he encountered the same issue with the delayed initialization of the field.<\/p>\n

    \"Enhancing<\/p>\n

    During his research, John came across the newly introduced formLoaded<\/strong> event in Microsoft\u2019s documentation. This event enables<\/strong> extra API calls once the form has fully loaded,<\/strong> making it ideal for cases where follow-up actions depend on fields that are set up during the initial form load.<\/p>\n

    By using the formLoaded<\/strong> event, we can apply methods like addLoaded <\/strong>and removeLoaded<\/strong>, which help attach or detach functions based on specific needs. In John’s case, he used formLoaded<\/strong> to link the tax calculation function after the “Salary” field was fully initialized.<\/p>\n

    Here\u2019s a reference code snippet that illustrates how I implemented this functionality.<\/p>\n

     \r\nasync function getAllEmployeeData(executionContext) {\r\n    try {\r\n\t  \/\/Retrieving the Employee's data using the external API \r\n        \/\/ Process each employee's data\r\n        const formContext = executionContext.getFormContext();\r\n        const managerNameData = formContext.getAttribute(\"new_manager\").getValue()[0];;\r\n        if (managerNameData == null) {\r\n            console.log(\"managerNameData is empty\");\r\n            return;\r\n        }\r\n        const managerName = managerNameData.name;\r\n        console.log(\"Manager name: \" + managerName);\r\n\r\n        const updatedEmployeeData = allEmployeeData.map((employee) => {\r\n            if (employee.new_name === managerName) {\r\n                formContext.getAttribute(\"new_salary\").setValue(employee.new_employee_salary);\r\n                console.log(\"Manager salary updated successfully\");\r\n            }\r\n            return employee;\r\n        });\r\n\r\n        \/\/ Update the monthly tax field\r\n        formContext.ui.addLoaded(calculateTax);\r\n    } catch (error) {\r\n        console.log(\"Error retrieving employee data: \" + error.message);\r\n    }\r\n    const endTime = performance.now();\r\n    console.log(`getAllEmployeeData execution time: ${endTime - startTime} milliseconds`);\r\n\r\n\r\n}\r\n\/**\r\n * Calculates the tax amount based on the employee salary.\r\n *\/\r\nfunction calculateTax() {\r\n    \/\/declaring the function level variables\r\n    const startTime = performance.now();\r\n    var taxAmount;\r\n    try {\r\n        const formContext = Xrm.Page.data;\r\n        const employeeSalary = formContext.entity.attributes.get(\"new_salary\").getValue();\r\n        if (employeeSalary !== null && employeeSalary !== \"\" && employeeSalary !== undefined) {\r\n            const taxRate = 0.25; \/\/ 25% tax rate\r\n            taxAmount = employeeSalary * taxRate;\r\n            formContext.entity.attributes.get(\"new_monthlytax\").setValue(taxAmount);\r\n            console.log(\"Tax calculation successful\");\r\n        } else {\r\n            console.log(\"Employee salary data is not present\");\r\n        }\r\n    } catch (error) {\r\n        console.error(\"Error in tax calculation:\", error.message);\r\n    }\r\n    const endTime = performance.now();\r\n    console.log(`calculateTax execution time: ${endTime - startTime} milliseconds`);\r\n}\r\nend<\/pre>\n
    This code clearly demonstrates how we can efficiently perform post operations on data initialized during the formLoaded event.<\/p>\n
    Advantages of Using the FormLoaded Event:<\/h3>\n
      \n
    1. Improved User Experience:<\/strong> Ensures all fields are ready for interaction.<\/li>\n
    2. Efficient Data Handling:<\/strong> Handles dependencies effectively, allowing for accurate post calculations.<\/li>\n
    3. Reduced Wait Times:<\/strong> Minimizes delays by managing data loading more efficiently.<\/li>\n<\/ol>\n
      Conclusion<\/strong><\/h2>\n
      In conclusion, adopting the formLoaded<\/strong> event has greatly improved our form handling processes. Initializing all data prior to user interaction has enhanced the reliability and performance of our applications. Now developers can easily consider this approach for optimizing their form handling strategies and delivering a superior user experience.<\/p>\n
      \"Model<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
      As developers, we understand that effective form handling is important for delivering a good user experience. Traditionally, many of us depend on \u201cformLoad\u201d, but this approach has significant drawbacks, such as inconsistent loading data and insufficient feedback during asynchronous data fetching, which can lead to user frustration. In many projects, the formLoaded method has proven\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":11,"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":[44],"tags":[2959],"class_list":["post-39587","post","type-post","status-publish","format-standard","hentry","category-power-apps","tag-formloaded-function"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/39587","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\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=39587"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/39587\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=39587"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=39587"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=39587"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}