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

Update Label or Control based on change from Text Input

In my current set up, I am working with a large On-Premise Database data set; TRUCKLOG : 40,000 records.  I display a limited amount of this data in a gallery, TRUCKGALLERY, based on filtered criteria where LOADS<>INVOICED. From here, I have users "form fill" other information with some editable TEXT INPUTS. The user then clicks the UPDATE button, which saves all updated information by creating a collection TRUCKCOLLECTION, and then click the SUBMIT button, which patches everything through to back to the database.

 

Problem: The above works fine, UNTIL my TRUCKGALLERY has more than 15 records. It takes forever because it is patching the whole TRUCKCOLLECTION,  even if there was no change in the record.  I was wondering of there is any way to identify and ONLY collect records that have been changed in the TRUCKGALLERY. 

 

Attempts: I added a label "RECORDCHANGE", and set this to "N".  I am currently trying to change it to "Y" whenever there is a change to any of the editable fields. This is so that when the user clicks UPDATE, the app can just collect the TRUCKGALLERY where RECORDCHANGE = "Y".  I have not been successful in doing this, because can not find anything that changes RECORDCHANGE to "Y". The closest I have reached with no errors was by adding 'CHANGERECORD'.Text = "Y" , to the OnChange field of the Editable Text Inputs, but it does absolutely nothing. 

 

Is there another property that can successfully change RECORDCHANGE to "Y"?

Is there perhaps another way to identify and ONLY collect records that have been changed in the TRUCKGALLERY? 

 

 

 

 

6 REPLIES 6
notj
Post Prodigy
Post Prodigy

If your text values are in an edit form, you can patch back just the form. This is much quicker.(Code Below).

If you're not using a form, you can still use the code below but your patch will look different where the forms are listed. You would just have your fields. 

 

I think you could probable benefit from reading up on the patch command. 
Patch function - Power Apps | Microsoft Docs

PowerApps Patch Function with examples - SPGuides

 

Patch(
        'TRUCKLOG',
        Defaults('TRUCKLOG'),
        Form1.Updates,
        Form4.Updates,
        Form5.Updates
    )

 

Ok, so this somewhat works. I didn't use any forms. I do not believe I can. I need to show my information in somewhat of a Excel Base View.

 

Material Display.PNG

 

It patches directly to the database with the following: 

 

ForAll(TRUCKGALLERY.AllItems,
(Patch(TRUCKLOG, ThisRecord,{Material: RPTJOBDET_MAT.Text, ETC.} )))

 

However it is still taking long if my Gallery displays 15+ Rows. I would prefer to collect only records that have been updated and then patch those through.  

notj
Post Prodigy
Post Prodigy

There's probably better ways to do this, but my initial thought is you need something that shows that the record has been modified and then you patch only those.

 

You could add a checkbox that the user will check  and then only patch records where the box is checked. 

 

If you don't want to have the user check the box, you can add some logic to evaluate if the record in the gallery has been modified and check the box automatically.

 

Then you would modify your patch to only patch records where the box is checked.

joeyb1215
Frequent Visitor

That is exactly what I am trying to do. 

From Initial Post: 

" I was wondering of there is any way to identify and ONLY collect records that have been changed in the TRUCKGALLERY. 

Attempts: I added a label "RECORDCHANGE", and set this to "N".  I am currently trying to change it to "Y" whenever there is a change to any of the editable fields. This is so that when the user clicks UPDATE, the app can just collect the TRUCKGALLERY where RECORDCHANGE = "Y".  I have not been successful in doing this, because can not find anything that changes RECORDCHANGE to "Y". The closest I have reached with no errors was by adding 'CHANGERECORD'.Text = "Y" , to the OnChange field of the Editable Text Inputs, but it does absolutely nothing. "

 

 The logic is what I currently need help with. I would like to not put the identification process in the hands of the user. I foresee a bunch of user errors with that. I also could not get the check box to work either. Do you have the proper code for that? Again I added 'CHANGERECORD'.Text  = "Y"  ('.Value = True' for the Check Box) , to the OnChange field of the Editable Text Inputs. It showed no errors but it did absolutely nothing. 

 

notj
Post Prodigy
Post Prodigy

There's a whole bunch of ways to do this, and I'm sure one is better than the others. 

 

We might be overthinking this. Why not just add the patch to the OnChange for the fields you want to keep track of?

 

Patch(
         TRUCKLOG,
         ThisItem,
          {
           HAULNUM: haultextbox.text
          }
))

Whenever you change the value, it patches that record back.

 

 

This was one of my first designs; it was very glitchy. After I entered my first field, I would  tab over to start filling other fields, and it would reset my inputs and and pull me out of focus. I imagine this was the writing that was taking place, and the data source refreshing after. I would have to click back into the fields and retype everything it reset, ultimately waiting close to 3 to 4 full seconds after every input. With the amount of data being entered, that can't happen. 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (600)