cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
JDS94
Frequent Visitor

Best practices for interaction with Outlook connector

Hi all, 

 

I'm working on a tool that permit to do desk reservations.

After selecting a date and time for meeting session, i have a "Confirm" button that permit to validate the room reservation.

At the same time, i want to create an event in Outlook 365 Calendar automatically. 

 

There's 2 ways to do this and for best practices reasons, i would like to know what is the best solution between : 

Solution 1 : From Power Apps, call a Power Automate that do this job

Solution 2 : From Power Apps, use the connector O365 Outlook direclty

 

What should be the best approach ?

 

Many thanks for help

1 ACCEPTED SOLUTION

Accepted Solutions
BCLS776
Super User
Super User

"Best practice" is a bit situational for this one. Both of the methods you describe use the same O365 connector to achieve the same functionality. Here are a few reasons to choose flows over calling a connector directly in your app:

  1. Maker-built functions are not something that is currently available in Power Apps, but flows make a pretty good replacement. Functional building blocks are a good practice to keep complex apps relatively bug-free and maintainable.
  2. Flows can handle more than the standard 500-2000 row limit imposed on Power Apps for performance reasons.
  3. Flows are good for delegating data & bandwidth-intensive operations so that the user's experience is as performant as possible

Flows take a bit of extra time to set up and test/debug, so there's a tradeoff. As well, calling a second service (Power Automate) to do something you can do in Power Apps can potentially slow your app down if it were quicker to call the connector directly from the app.

In your case, you're probably calling this connector once every time the user presses the button. As well the O365 connector typically does not handle many rows of data. So, you're likely better off simply calling the connector directly in your app.

 

Hope that helps,

Bryan

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a Thumbs Up.

View solution in original post

1 REPLY 1
BCLS776
Super User
Super User

"Best practice" is a bit situational for this one. Both of the methods you describe use the same O365 connector to achieve the same functionality. Here are a few reasons to choose flows over calling a connector directly in your app:

  1. Maker-built functions are not something that is currently available in Power Apps, but flows make a pretty good replacement. Functional building blocks are a good practice to keep complex apps relatively bug-free and maintainable.
  2. Flows can handle more than the standard 500-2000 row limit imposed on Power Apps for performance reasons.
  3. Flows are good for delegating data & bandwidth-intensive operations so that the user's experience is as performant as possible

Flows take a bit of extra time to set up and test/debug, so there's a tradeoff. As well, calling a second service (Power Automate) to do something you can do in Power Apps can potentially slow your app down if it were quicker to call the connector directly from the app.

In your case, you're probably calling this connector once every time the user presses the button. As well the O365 connector typically does not handle many rows of data. So, you're likely better off simply calling the connector directly in your app.

 

Hope that helps,

Bryan

_________________________________________________________________________________________
Help the community help more users by choosing to "Accept as Solution" if this post met your needs. If you liked the post and want to show some appreciation, please give it a Thumbs Up.

Helpful resources

Announcements
PA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.

Microsoft Build 768x460.png

Microsoft Build is May 24-26. Have you registered yet?

Come together to explore latest innovations in code and application development—and gain insights from experts from around the world.

May UG Leader Call Carousel 768x460.png

What difference can a User Group make for you?

At the monthly call, connect with other leaders and find out how community makes your experience even better.

Top Solution Authors
Top Kudoed Authors
Users online (3,279)