Hello,
I have a Canvas App linked to a Dataverse Table,
in the App the user can edit Values (Project Status Tracking),
I've more or less finished the user Interface now.
My question - how do you guys check if a user did changes on the values?
1. to know if patching is required
2. to prevent user deleting entered values unintentionally (in my case i have a next button to load next row of Content)
"simplest" but not effective way is prob. to compare Input boxes with Dataverse values,
but is there something "global" - for example - just check if user clicked things or did hit keyboard, or something like that?
best Regards
Thomas
Solved! Go to Solution.
Hi @thsteh there are multiple way you could achieve this:
1. Track Changes in Input Fields: One straightforward approach is to compare the current values in the input fields with the original values fetched from the Dataverse table. You can create a variable for each input field that stores the original value and then compare it to the current value when needed. If the current and original values differ, you'll know changes have been made.
OnVisible: UpdateContext({ OriginalValue: DataTable.Selected.Value })
Then, you can use a formula like this to determine whether changes have been made:
!IsBlank(DataTable.Selected.Value) && DataTable.Selected.Value <> OriginalValue
2. Using a Dirty Flag: Implement a "dirty flag" variable that gets set to true whenever a change is made. You can use this flag to determine whether changes have been made that require saving or patching.
OnChange or OnSelect: UpdateContext({ IsDirty: true })
And then, use the IsDirty variable to control actions like enabling/disabling buttons.
3. Keyboard or Interaction Event Tracking: You can use the OnKeyDown or OnTextInput events to trigger a flag indicating that the user is interacting with the app. However, this approach might not be very precise, as it would trigger even if the user is just navigating through fields.
OnKeyDown or OnTextInput: UpdateContext({ IsUserInteracting: true })
Keep in mind that this approach might require more detailed implementation to correctly detect user interactions.
4. Saving Unchanged Data: If you're concerned about data loss due to accidental deletion while navigating through records, you can implement an approach where you save the data for the current record before moving to the next record, regardless of whether changes were made. This way, even if the user accidentally navigates away from the record, the entered data remains saved.
These strategies can be used in combination to create a comprehensive mechanism for tracking changes and interactions in your Canvas App. Choose the approach that best fits your app's workflow and user experience while ensuring data integrity and user-friendly behavior.
@thsteh same concept. You will need to compare proposed/changed value with the existing saved/default value.
As a simple example, suppose we want to change the BorderColor property for a Text Input control if the Default value is different from the entered value. For the Default property of the Text Input control, we have:
Gallery1.Selected.'Some Text Field'
And then in the BorderColor property, we can use:
If(
Gallery1.Selected.'Some Text Field' <> Self.Text,
Color.Red,
Color.Transparent
)
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
Hi @thsteh - the best and simplest method in my opinion is to use a Form control to validate changes.
Two key properties of a DataCard are the Default and Update properties.
You can check whether Default property and Update properties of the DataCard shares the same value. If they do not, then you can visually demonstrate to the user what has and has not been changed from the existing data held in the Form.
For example, I could set the BorderColor property of the DataCard to Color.Red when a change has been made to a Text field:
If(
Self.Default <> Self.Update && Parent.Mode = FormMode.Edit,
Color.Red,
Color.Transparent
)
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
Hi @thsteh there are multiple way you could achieve this:
1. Track Changes in Input Fields: One straightforward approach is to compare the current values in the input fields with the original values fetched from the Dataverse table. You can create a variable for each input field that stores the original value and then compare it to the current value when needed. If the current and original values differ, you'll know changes have been made.
OnVisible: UpdateContext({ OriginalValue: DataTable.Selected.Value })
Then, you can use a formula like this to determine whether changes have been made:
!IsBlank(DataTable.Selected.Value) && DataTable.Selected.Value <> OriginalValue
2. Using a Dirty Flag: Implement a "dirty flag" variable that gets set to true whenever a change is made. You can use this flag to determine whether changes have been made that require saving or patching.
OnChange or OnSelect: UpdateContext({ IsDirty: true })
And then, use the IsDirty variable to control actions like enabling/disabling buttons.
3. Keyboard or Interaction Event Tracking: You can use the OnKeyDown or OnTextInput events to trigger a flag indicating that the user is interacting with the app. However, this approach might not be very precise, as it would trigger even if the user is just navigating through fields.
OnKeyDown or OnTextInput: UpdateContext({ IsUserInteracting: true })
Keep in mind that this approach might require more detailed implementation to correctly detect user interactions.
4. Saving Unchanged Data: If you're concerned about data loss due to accidental deletion while navigating through records, you can implement an approach where you save the data for the current record before moving to the next record, regardless of whether changes were made. This way, even if the user accidentally navigates away from the record, the entered data remains saved.
These strategies can be used in combination to create a comprehensive mechanism for tracking changes and interactions in your Canvas App. Choose the approach that best fits your app's workflow and user experience while ensuring data integrity and user-friendly behavior.
@thsteh same concept. You will need to compare proposed/changed value with the existing saved/default value.
As a simple example, suppose we want to change the BorderColor property for a Text Input control if the Default value is different from the entered value. For the Default property of the Text Input control, we have:
Gallery1.Selected.'Some Text Field'
And then in the BorderColor property, we can use:
If(
Gallery1.Selected.'Some Text Field' <> Self.Text,
Color.Red,
Color.Transparent
)
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
------------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved. Remember, you can accept more than one post as a solution.
If you like my response, please give it a Thumbs Up.
Imran-Ami Khan
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!
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
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.
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