cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
BrendonBrooksP1
Post Patron
Post Patron

SQL Data Spikes

Hello,

 

For the past few weeks I have been having recurring issues where a user tries to update multiple records and often fails doing so. This has happend quite a few times within the last week.

 

I have three tables that get updated within SQL: Inspections, Records, Items. This issue always happens to my Inspections table, which messes up the associated View. 

 

Here's the code that I use when a user updates a record:

Concurrent(
    Patch(
        '[dbo].[Inspections]',
        First(
            Filter(
                '[dbo].[Inspections]',
                Id = Value(InspectIdHome.Text)
            )
        ),
        {
            Base: DropBaseInspHome.Selected.Value,
            Unit: DropUnitInspHome.Selected.Value,
            TailNumber: DropTailNumInspHome.Selected.Value,
            Location: DropLocInspHome.Selected.Value,
            NextInspect: DateValue(LblNextInspect_2.Text),
            LastInspectionDate: DatePickMaintenance_2.SelectedDate,
            Status: DropStatusInspHome.Selected.Value
        }
    ),
    Patch(
        '[dbo].[Records]',
        Defaults('[dbo].[Records]'),
        {
            alseSn:  SerialInspHome.Text,
            Base: DropBaseInspHome.Selected.Value,
            Description: TxtBoxDescription_2.Text,
            Inspector: DropInspectorInspHome1.Selected.Value,
            Inspector2: DropInspectorInspHome2.Selected.Value,
            Location: DropLocInspHome.Selected.Value,
            maintAccomplishDate: DatePickMaintenance_2.SelectedDate,
            Type: "Inspect",
            Status: DropStatusInspHome.Selected.Value,
            TailNumber: DropTailNumInspHome.Selected.Value
        }
    ),
    Patch(
        '[dbo].[ Items]',
        First(
            Filter(
                '[dbo].[alseItems]',
                Id = Value(ItemIdHome.Text)
            )
        ),
        {
            Base: DropBaseInspHome.Selected.Value,
            Unit: DropUnitInspHome.Selected.Value,
            location: DropLocInspHome.Selected.Value,
            tailNumber: DropTailNumInspHome.Selected.Value,
            status: DropStatusInspHome.Selected.Value
        }
    )
);
Navigate(
    Success,
    ScreenTransition.Cover
)

It's been very difficult for me to recreate this error. Upon reviewing Azure, I did notice several data spikes where my utilization went up to nearly 100%:

DataUsage.PNG

 

Once a user saves a record, it will make a call to Refresh the database connection as follows:

 

Refresh('[dbo].[Inspections]')

What could cause this issue? I have at most, 3 users on a 100mb network connection. I know PowerApps can be a resource hog, but it shouldn't be this difficult. Thank you.

 

Brendon

1 ACCEPTED SOLUTION

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @BrendonBrooksP1 ,

Could you please share more details about the error message with your formula?

How do you collect the data entered via the users in your app? Using Edit form control or just a set of simple controls?

Have you taken a try to remove the Concurrent() function and perform your formula again?

 

If you collect the data entered via the users in your app using a set of simple controls (e.g. Dropdown, Text Input box, etc) rather than Edit form, please modify your formula as below:

 

Patch(
        '[dbo].[Inspections]',
        LookUp('[dbo].[Inspections]', Id = Value(InspectIdHome.Text)),
        {
            Base: DropBaseInspHome.Selected.Value,
            Unit: DropUnitInspHome.Selected.Value,
            TailNumber: DropTailNumInspHome.Selected.Value,
            Location: DropLocInspHome.Selected.Value,
            NextInspect: DateValue(LblNextInspect_2.Text),
            LastInspectionDate: DatePickMaintenance_2.SelectedDate,
            Status: DropStatusInspHome.Selected.Value
        }
);
Patch(
        '[dbo].[Records]',
        Defaults('[dbo].[Records]'),
        {
            alseSn:  SerialInspHome.Text,
            Base: DropBaseInspHome.Selected.Value,
            Description: TxtBoxDescription_2.Text,
            Inspector: DropInspectorInspHome1.Selected.Value,
            Inspector2: DropInspectorInspHome2.Selected.Value,
            Location: DropLocInspHome.Selected.Value,
            maintAccomplishDate: DatePickMaintenance_2.SelectedDate,
            Type: "Inspect",
            Status: DropStatusInspHome.Selected.Value,
            TailNumber: DropTailNumInspHome.Selected.Value
        }
);
Patch(
        '[dbo].[ Items]',
        LookUp('[dbo].[alseItems]',Id = Value(ItemIdHome.Text)),
        {
            Base: DropBaseInspHome.Selected.Value,
            Unit: DropUnitInspHome.Selected.Value,
            location: DropLocInspHome.Selected.Value,
            tailNumber: DropTailNumInspHome.Selected.Value,
            status: DropStatusInspHome.Selected.Value
        }
);
Navigate(
    Success,
    ScreenTransition.Cover
)

please take a try with above formula, then check if the issue is solved.

 

If you collect the data entered via the users in your app using Edit form, please consider modify your formula as below:

Set(EntryData, EditForm1.Updates);   /* <-- Store the filled Forms data into a variable, then reference corresponding values from this variable within your Patch function*/
Patch( '[dbo].[Inspections]', LookUp('[dbo].[Inspections]', Id = Value(InspectIdHome.Text)), { Base: EntryData.Base, Unit: EntryData.Unit, TailNumber: EntryData.TailNumber, ... } ); Patch( '[dbo].[Records]', Defaults('[dbo].[Records]'), { alseSn: EntryData.alesSn, Base: EntryData.Base, Description: EntryData.Description, Inspector: EntryData.Inspector, ... } ); Patch( '[dbo].[ Items]', LookUp('[dbo].[alseItems]',Id = Value(ItemIdHome.Text)), { Base: EntryData.Base, Unit: EntryData.Unit, location: EntryData.location, tailNumber: EntryData.tailNumber, status: EntryData.status } ); Navigate( Success, ScreenTransition.Cover )

Note: If your three Patch functions reference values from multiple Edit forms, please consider take a try to save these multiple form data into separated variables (e.g. EntryData, EntryData1, EntryData2, ...). Then within your Patch formula, reference values from proper variable.

 

Best regards,

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

5 REPLIES 5
RandyHayes
Super User
Super User

@BrendonBrooksP1 

I'm not entirely sure if your post is a question on the problem you are having with the formula you posted or if it is the spikes.

I'm addressing more of the situation that you are having in regard to your posted formula.  

You mentioned "...update multiple records and often fails doing so." - can you go into more detail on this?  What fails and what happens when it fails?

 

So, in looking at your formula, I do notice a couple things that you might want to consider.

1) Your first patch statement to Inspections - you might want to do a Lookup('[dbo].[Inspections]', Id=Value(InspectIdHome.Text) rather than the Filter and First statement.  This will return essentially the same results, but with less formula. (This goes for your 3rd Patch formula as well)

2) In regard to that last formula in 1...I always see a red-flag when casting an ID from text.  Probably all good...but, if you have some other place that you have the ID as the true ID, I'd use that for your filter.  (This goes for your 3rd Patch formula as well)

3) You should consider checking for errors.  Since you have dependencies on all of these tables - if you were to do true transactions - you would check errors and rollback if there were issues.  But, short of that, at least check errors between patch statements.

4) Also in regard to 3, you end with a navigate to a Success screen, but again, no actual check for any error conditions.

 

Hopefully this will provide some fuel for thought, and at the least you can put some checking in the formula and perhaps see where the issues are coming from.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

You mentioned "...update multiple records and often fails doing so." - can you go into more detail on this?  What fails and what happens when it fails?

-The user selects a single item, and then performs and inspection. The user fills out data (location, description etc) and then clicks on a button that saves the record. What ends up happening is that the Inspections table never receives the update. The other two tables (Item and Records) have no problems and are updated. 

 

I'm not entirely sure if your post is a question on the problem you are having with the formula you posted or if it is the spikes.

I guess I'm having a problem with both? I'm trying to figure out if they're related or not. 

 

1) Your first patch statement to Inspections - you might want to do a Lookup('[dbo].[Inspections]', Id=Value(InspectIdHome.Text) rather than the Filter and First statement.  This will return essentially the same results, but with less formula. (This goes for your 3rd Patch formula as well)

-I suppose I could use the LookUp function if that speeds things or simply makes the code easier to read. I'll give that a shot this week.

 

2) In regard to that last formula in 1...I always see a red-flag when casting an ID from text.  Probably all good...but, if you have some other place that you have the ID as the true ID, I'd use that for your filter.  (This goes for your 3rd Patch formula as well)

-My current formula makes a call to get the ID of a record, and then uses that as a reference when I Patch. Again, I probably could get away with just using a LookUp function, or by using the Serial Number of the item instead of the ID.

 

3) You should consider checking for errors.  Since you have dependencies on all of these tables - if you were to do true transactions - you would check errors and rollback if there were issues.  But, short of that, at least check errors between patch statements.

Error checking has the be bane of my existence with PowerApps. I'm still fairly confused on how to incorporate them into any of my formuals. 

 

Thanks for the feedback

-Brendon

 

v-xida-msft
Community Support
Community Support

Hi @BrendonBrooksP1 ,

Could you please share more details about the error message with your formula?

How do you collect the data entered via the users in your app? Using Edit form control or just a set of simple controls?

Have you taken a try to remove the Concurrent() function and perform your formula again?

 

If you collect the data entered via the users in your app using a set of simple controls (e.g. Dropdown, Text Input box, etc) rather than Edit form, please modify your formula as below:

 

Patch(
        '[dbo].[Inspections]',
        LookUp('[dbo].[Inspections]', Id = Value(InspectIdHome.Text)),
        {
            Base: DropBaseInspHome.Selected.Value,
            Unit: DropUnitInspHome.Selected.Value,
            TailNumber: DropTailNumInspHome.Selected.Value,
            Location: DropLocInspHome.Selected.Value,
            NextInspect: DateValue(LblNextInspect_2.Text),
            LastInspectionDate: DatePickMaintenance_2.SelectedDate,
            Status: DropStatusInspHome.Selected.Value
        }
);
Patch(
        '[dbo].[Records]',
        Defaults('[dbo].[Records]'),
        {
            alseSn:  SerialInspHome.Text,
            Base: DropBaseInspHome.Selected.Value,
            Description: TxtBoxDescription_2.Text,
            Inspector: DropInspectorInspHome1.Selected.Value,
            Inspector2: DropInspectorInspHome2.Selected.Value,
            Location: DropLocInspHome.Selected.Value,
            maintAccomplishDate: DatePickMaintenance_2.SelectedDate,
            Type: "Inspect",
            Status: DropStatusInspHome.Selected.Value,
            TailNumber: DropTailNumInspHome.Selected.Value
        }
);
Patch(
        '[dbo].[ Items]',
        LookUp('[dbo].[alseItems]',Id = Value(ItemIdHome.Text)),
        {
            Base: DropBaseInspHome.Selected.Value,
            Unit: DropUnitInspHome.Selected.Value,
            location: DropLocInspHome.Selected.Value,
            tailNumber: DropTailNumInspHome.Selected.Value,
            status: DropStatusInspHome.Selected.Value
        }
);
Navigate(
    Success,
    ScreenTransition.Cover
)

please take a try with above formula, then check if the issue is solved.

 

If you collect the data entered via the users in your app using Edit form, please consider modify your formula as below:

Set(EntryData, EditForm1.Updates);   /* <-- Store the filled Forms data into a variable, then reference corresponding values from this variable within your Patch function*/
Patch( '[dbo].[Inspections]', LookUp('[dbo].[Inspections]', Id = Value(InspectIdHome.Text)), { Base: EntryData.Base, Unit: EntryData.Unit, TailNumber: EntryData.TailNumber, ... } ); Patch( '[dbo].[Records]', Defaults('[dbo].[Records]'), { alseSn: EntryData.alesSn, Base: EntryData.Base, Description: EntryData.Description, Inspector: EntryData.Inspector, ... } ); Patch( '[dbo].[ Items]', LookUp('[dbo].[alseItems]',Id = Value(ItemIdHome.Text)), { Base: EntryData.Base, Unit: EntryData.Unit, location: EntryData.location, tailNumber: EntryData.tailNumber, status: EntryData.status } ); Navigate( Success, ScreenTransition.Cover )

Note: If your three Patch functions reference values from multiple Edit forms, please consider take a try to save these multiple form data into separated variables (e.g. EntryData, EntryData1, EntryData2, ...). Then within your Patch formula, reference values from proper variable.

 

Best regards,

 

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@BrendonBrooksP1 

I would focus on that one patch that doesn't seem to work all the time. Perhaps that would be a good place to look at the Errors function to check if there is an issue before proceeding to the next patch.

Basically you can do an IsEmpty(Errors('[dbo].[Inspections]') right after that patch and see if there is an error.  Then proceed as appropriate. 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

I removed the Concurrent() command and everything works. Should we not use Concurrent() to Patch multiple tables at once? I had thought that the command would speed up the patching proccess, but apparently it just causes more problems than they're worth. Thanks again @RandyHayes and @v-xida-msft . I appreciate your help. 

 

Brendon

Helpful resources

Announcements

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!      

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Community Roundup: A Look Back at Our Last 10 Tuesday Tips

As we continue to grow and learn together, it's important to reflect on the valuable insights we've shared. For today's #TuesdayTip, we're excited to take a moment to look back at the last 10 tips we've shared in case you missed any or want to revisit them. Thanks for your incredible support for this series--we're so glad it was able to help so many of you navigate your community experience!   Getting Started in the Community An overview of everything you need to know about navigating the community on one page!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Ranks and YOU Have you ever wondered how your fellow community members ascend the ranks within our community? We explain everything about ranks and how to achieve points so you can climb up in the rankings! Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Powering Up Your Community Profile Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Blogs--A Great Place to Start There's so much you'll discover in the Community Blogs, and we hope you'll check them out today!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Unlocking Community Achievements and Earning Badges Across the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. Check out some details on Community badges--and find out more in the detailed link at the end of the article! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Blogging in the Community Interested in blogging? Everything you need to know on writing blogs in our four communities! Get started blogging across the Power Platform communities today! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Subscriptions & Notifications We don't want you to miss a thing in the community! Read all about how to subscribe to sections of our forums and how to setup your notifications! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Getting Started with Private Messages & Macros Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Community User Groups Learn everything about being part of, starting, or leading a User Group in the Power Platform Community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Update Your Community Profile Today! Keep your community profile up to date which is essential for staying connected and engaged with the community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Thank you for being an integral part of our journey.   Here's to many more Tuesday Tips as we pave the way for a brighter, more connected future! As always, watch the News & Announcements for the next set of tips, coming soon!

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Welcome to the Power Apps Community

Welcome! Congratulations on joining the Microsoft Power Apps community! You are now a part of a vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun! Now that you are a member, you can enjoy the following resources:   The Microsoft Power Apps Community Forums If you are looking for support with any part of Microsoft Power Apps, our forums are the place to go. They are titled "Get Help with Microsoft Power Apps " and there you will find thousands of technical professionals with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Apps community forums! Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered!   Microsoft Power Apps IdeasDo you have an idea to improve the Microsoft Power Apps experience, or a feature request for future product updates? Then the "Power Apps Ideas" section is where you can contribute your suggestions and vote for ideas posted by other community members. We constantly look to the most voted Ideas when planning updates, so your suggestions and votes will always make a difference.   Community Blog & NewsOver the years, more than 600 Power Apps Community Blog Articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on building Power Apps. On the Power Apps Community Blog, read the latest Power Apps related posts from our community blog authors around the world. Let us know if you would like to become an author and contribute your own writing — everything Power Apps related is welcome!   Power Apps Samples, Learning and Videos GalleriesOur galleries have a little bit of everything to do with Power Apps. Our galleries are great for finding inspiration for your next app or component. You can view, comment and kudo the apps and component gallery to see what others have created! Or share Power Apps that you have created with other Power Apps enthusiasts. Along with all of that awesome content, there is the Power Apps Community Video & MBAS gallery where you can watch tutorials and demos by Microsoft staff, partners, and community gurus in our community video gallery.   Again, we are excited to welcome you to the Microsoft Power Apps community family! Whether you are brand new to the world of process automation or you are a seasoned Power Apps veteran. Our goal is to shape the community to be your ‘go to’ for support, networking, education, inspiration and encouragement as we enjoy this adventure together!   Let us know in the Community Feedback if you have any questions or comments about your community experience.To learn more about the community and your account be sure to visit our Community Support Area boards to learn more! We look forward to seeing you in the Power Apps Community!The Power Apps Team

Top Solution Authors
Top Kudoed Authors
Users online (5,256)