cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
UB400
Level 10

Re: Checking to see if a Record exists, if it does then Patch an update, if not then create a new re

@bdc604 you can now increase the limit beyond 500 records (upto 2000 I believe). I can understand your frustration, but not the sentiment you express. With a little exploration and help from the great community here, it's amazing what one can achieve with PowerApps, there's no shortage of amazing Apps that have been built by members of the communiy here.

 

If you're just trolling, then I suggest you do it elsewhere. The PowerApps community has by far the best and most helpful members I've come across anywhere.

JeremyDIV
Level: Powered On

Re: Checking to see if a Record exists, if it does then Patch an update, if not then create a new re

The EXPERIMENTAL 2000 row limit is equally arbitrary and almost as prohibitive as 500. I have not been able to get the feature to perform correctly (but there are no guaranties with experimental features).

 

I think the frustration is more than fair. @bdc604 is not attacking the PowerApps community. He or she is holding up a mirror to the flaws in a badly formed (or at the very least prematurely released) product that has developers writing work arounds to accomplish basic tasks.

Highlighted
bdc604
Level 8

Re: Checking to see if a Record exists, if it does then Patch an update, if not then create a new re

Heres a question; has SharePoint delegation been resolved yet? That is, having SharePoint perform any filtering requirements on the backend and returning only the result? I'm finding conflicting answers online; yes it has, no it hasn't.

 

If I have a list with 5000 items and only need to return 1 based on a filter condition, will PowerApps (or Flow for that matter) give up after looking at the first 500 (or first 2000) and say 'meh, I tried, couldn't find it', even though it is actually there?

nickduxfield
Level 8

Re: Checking to see if a Record exists, if it does then Patch an update, if not then create a new re

You may simply hide a submit button based on a filter query.
Your filter should narrow down to a collection of 50 items that you can query against to be helpful.
Using date fields, author.email and submission status should narrow it effectively. As a user may only ever sumit up to 500 items in a given week.

You can easily collect a distinct collection of these 3 columns to compare using the in operator.
aweaver
Level: Power Up

Re: Checking to see if a Record exists, if it does then Patch an update, if not then create a new record

I am looking for a similar solution. I have two tables. Table A has one email and one phone number column. I need to perform a lookup in another table, Table B. Table B has 4 different phone number columns (home, work, cell, other) and two different email (home and work). I need table A to run essentially a conditional lookup on table B, for 4 different columns on the phone and then 2 columns for the email and then return a boolean value. Thoughts?.

Helpful resources

Announcements
thirdimage

Power Apps Community User Group Member Badge

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

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

SecondImage

Difinity Conference

The largest Power BI, Power Platform, and Data conference in New Zealand

Top Solution Authors
Top Kudoed Authors (Last 30 Days)
Users online (5,611)