Fast And Slow Patching in Canvas App

| Faiza Umair

Patching in Canvas app can be done in different ways. But the main concern of developer is to deal with speed of operation with all basic requirements fulfillments.

Patch() with ForAll() is taking more process time then Patch() direct statement.

Let’s look into some example to get more deeper and clearer look.

If we have survey for pets and want to insert data in dataverse table using both options one by one.

First get data on App Start

Fast-And-Slow-Patching-in-Canvas-App

Bind Gallery with Collection

Fast-And-Slow-Patching-in-Canvas-App

Add Code for Slow Patching with time difference calculation

Fast-And-Slow-Patching-in-Canvas-App

Now Add code for Fat Patching with time difference calculation

Fast-And-Slow-Patching-in-Canvas-App

Now Its time to find the result. Here is the result of slow patching

Fast-And-Slow-Patching-in-Canvas-App

And the result of Fast patching is

Fast-And-Slow-Patching-in-Canvas-App

Slow patching executes in 8417 milliseconds while fast patching executes 62 milliseconds

Note: Number of column in collection should be at least 2 because in fast patching we need unique identifier key in collection to match with record in dataverse table


Join us next time, as we continue our journey of learning canvas apps.Click here to learn more about Imperium's Power Apps Services. We hope this information was useful, and we look forward to sharing more insights into the Power Platform world.


M
Chief Architect, Founder, and CEO - a Microsoft recognized Power Platform solution architect.

About The Blog

Stay updated with what is happening in the Microsoft Business Applications world and initiatives Imperium is taking to ease digital transformation for customers.


More About Us

We provide guidance and strategic oversight to C-Suite and IT Directors for on-going implementations. Feel free to give us a call.

1 331 250 27 17
Send A Message

Ready to Start?

Get a personalized consultation for your project.

Book a Meeting