cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Helper I
Helper I

Handle Failed O365 Connector messages

Hi All,

In my App OnStart I am setting up some variables. One such variable is to get the Line Manager of the current User. It worked fine except for those Users who do not have a Line Manager registered in Azure. So I amended the code to this

 

 

Set(
varManager,
If(
IsBlank(Office365Users.ManagerV2(User().Email)),
"No Manager Listed",
Office365Users.ManagerV2(User().Email).displayName)
);

 

 

Again, works great. But, whenever the app loads, if the current user does not have a Line Manager, I still get the attached error. Any idea how I can handle this so it does not appear. Assigning a Line Manager is not an option I'm afraid. 

 

Many thanks,

Colz

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Memorable Member
Memorable Member

Re: Handle Failed O365 Connector messages

Hi Adzocol,

 

As I tried Different Ways for this Issue, I found this workaround for your Issue.

Workaround. - Create a Flow and Get this Details from Flow. and Call that flow in App Load.
if you Want you can also use the below-attached flow, that I created for this Testing Purpose.

Hope this Workaround will resolve your issue.

VijayTailor_0-1600598229612.png

 Paste the below Code in App Load Section.
Set(getManager,'TestManagerName'.Run(User().Email).managername);
On Screen

VijayTailor_0-1600598766756.png

 

 
 
 

 

Also, Find the TestingApp Create for this Issue If required.

VijayTailor_1-1600598332132.png

 



if you accept this as a solution, please mark this post as Answered.




 

View solution in original post

3 REPLIES 3
Highlighted
Helper I
Helper I

Re: Handle Failed O365 Connector messages

Anyone have any idea how to handle this? It doesn't break anything but just doesn't look great to Users of the app. I can't quite understand why it doesn't return 'null'. if the object doesn't exist. At least I could handle that in an elegant way and the User is unaware.

ManagerV2Error.JPG

 

Highlighted
Memorable Member
Memorable Member

Re: Handle Failed O365 Connector messages

Hi Adzocol,

 

As I tried Different Ways for this Issue, I found this workaround for your Issue.

Workaround. - Create a Flow and Get this Details from Flow. and Call that flow in App Load.
if you Want you can also use the below-attached flow, that I created for this Testing Purpose.

Hope this Workaround will resolve your issue.

VijayTailor_0-1600598229612.png

 Paste the below Code in App Load Section.
Set(getManager,'TestManagerName'.Run(User().Email).managername);
On Screen

VijayTailor_0-1600598766756.png

 

 
 
 

 

Also, Find the TestingApp Create for this Issue If required.

VijayTailor_1-1600598332132.png

 



if you accept this as a solution, please mark this post as Answered.




 

View solution in original post

Highlighted
Helper I
Helper I

Re: Handle Failed O365 Connector messages

Hi Vijay,

 

Genius. Works a treat my friend. Thank you very much for this. 

 

Best regards,

Col

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Find your favorite faces from the community presenting at the Power Platform Community Conference!

Watch Now

Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV Studio

Power Platform ISV Studio

ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Top Solution Authors
Top Kudoed Authors
Users online (9,525)