cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Super User
Super User

Adding third statement to a Concurrent() causes error.

This is a new phenomena...

 

This concurrent statement works perfect, and has for some time.

Concurrent(ClearCollect(MDL_All_Pre2,Get_MDData_4Lane2.Run()),ClearCollect(ACCT_Data_All,Get_AcctOnly_4Lane.Run()))

This is also a legit statement

ClearCollect(DPM_Pending,Filter('[dbo].[VIEW_SUB_PDM_PARTNUMBER_LATEST]',CurrentStatusID=11 Or CurrentStatusID=9))

However, when I try to put the 2nd statement inside the concurrent, I get an error:

image.png

I even get an error if I put the statement in the OnStart after the Concurrent(), and STILL get the error!  Without the statement, Get_MDData_4Lane2.Run() works fine.  The data sources are not related.

image.png

 

I have seen this statement recently in another app.  It was not related to a concurrent, and it only affected ONE user.  So strange.   My apps do have MANY connections, Flow .Run calls, etc.  Is there some limit being exceeded here?

 

Any ideas??

1 ACCEPTED SOLUTION

Accepted Solutions
Super User
Super User

Re: Adding third statement to a Concurrent() causes error.

@Akatamaoka ,

 

THanks for the reply.  This one goes back a ways.  It was one of the strangest issues i've had because it only affected a single user.  The flow connection certainly was properly connected.  In fact, this function worked perfectly for several other users.  I think this was going on during one of the times system outages were happening rather random and was affecting some connectors.  I have not tried to put the thirst statement back where it really belongs since then.  However, its one of those cases where its working, so I'm not going to fuss with it at this point.

 

Regards!

2 REPLIES 2
Highlighted
Akatamaoka
Level: Powered On

Re: Adding third statement to a Concurrent() causes error.

Is Get_MDData_4Lane2 a Microsoft Flow that hasn't been connected to the app? Does it appear as a connection when you go to View > Data Sources?

If that formula runs when a button is clicked or something, generally what I like to do is select the button, then click the Action menu and Flows and select the Flow from there to ensure it is connected correctly. I don't know if that would work for your situation...that's the only thing I can think of without more information.

Super User
Super User

Re: Adding third statement to a Concurrent() causes error.

@Akatamaoka ,

 

THanks for the reply.  This one goes back a ways.  It was one of the strangest issues i've had because it only affected a single user.  The flow connection certainly was properly connected.  In fact, this function worked perfectly for several other users.  I think this was going on during one of the times system outages were happening rather random and was affecting some connectors.  I have not tried to put the thirst statement back where it really belongs since then.  However, its one of those cases where its working, so I'm not going to fuss with it at this point.

 

Regards!

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

PowerApps Monthly Community Call

Next Wednesday, September 18th at 8am PDT

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

SecondImage

Power Platform Summit North America

Register by September 5 to save $200

Users Online
Currently online: 54 members 4,452 guests
Please welcome our newest community members: