cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Avoid duplicate values even when the form is in Edit mode

Hi All,

So, on the Report Name field, I have a label "Error 2- Report Name" whose Visible property is set to 
LookUp(Business_Requirement_Document, 'Report Name'='Value- Report Name'.Text, true) && (RH_SP_Form.Mode = FormMode.New)

What that does is- If the form is in new mode and if somebody tries to enter a report name that exists already, it shows an error which is controlled by the label's text property "Report name is already in use"

Now, what is happening is that if somebody goes to the form in edit mode by selecting any list item- and in the form changes the Report Name to a pre-existing value, it does not show an error because of the formula above having form mode set to "New". It then doesn't submit the form when we try to and shows the old values. How can I show the error here even while being in an edit mode.

If i am removing the condition (RH_SP_Form.Mode = FormMode.New) from the form- then it shows that error for every existing report even in view mode- which i don't want to see.

Kindly suggest!

@RandyHayes _ Can you please help resolve this?

1 ACCEPTED SOLUTION

Accepted Solutions

@Anonymous 
Change your visible formula to the following:

LookUp(Business_Requirement_Document, 'Report Name'='Value- Report Name'.Text, true) && ((RH_SP_Form.Mode = FormMode.New) || !(Parent.'Report Name' = 'Value- Report Name'.Text))

This will first lookup the record to determine if it exists.  If that is true, then it will be up to the form mode or the entered value not being the original value.

 

You do not need to duplicate true and false with an if condition for a true/false property.  It's just extra typing.

 

I hope this is helpful for you.

_____________________________________________________________________________________
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!

View solution in original post

12 REPLIES 12

Can you try adding the OR condition? like this:

RH_SP_Form.Mode = FormMode.New || RH_SP_Form.Mode = FormMode.Edit


Follow me on Twitter


Connect with me on LinkedIn


If you found my answer helpful, please consider giving it a thumbs-up or a like.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Pstork1
Most Valuable Professional
Most Valuable Professional

Unlock the card that holds the report name and use the following to set the display mode of that card to View when the form is in Edit mode.

if(RH_SP_Form.Mode = FormMode.New,Parent.DisplayMode,DisplayMode.View)

That will keep users from editing existing Report names.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Anonymous
Not applicable

@zmansuri This did not work.

Because, when form is in edit mode- it is checking against itself and showing the error by default in edit mode

GauravG_0-1622655351977.png

I should not check against itself but other values when in edit mode. What do you think?

Anonymous
Not applicable

@Pstork1 Great idea, you always have unconventional ways to help. I truly appreciate it.

I will pass on this idea to my lead. 

But I am expecting 'em to say that the report name should be editable in future even if it's once published and so the field should not be restricted to View only.

How should i proceed? I do not want to use the NOTIFY function on the form failure property as that would mean having 2 controls govern 1 error

Pstork1
Most Valuable Professional
Most Valuable Professional

You didn't mention what data source it is.  But if its SharePoint then you could do an error message and set the displaymode on the submit button to disable if you do a lookup on the report name and the ID of the list item in the lookup isn't null but doesn't match the ID of the record being edited.  That would indicate a duplicate report title.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Anonymous
Not applicable

I was not able to follow that unfortunately. Mind sharing the formula

Pstork1
Most Valuable Professional
Most Valuable Professional

Put the following in the error label visible property

 

With({Dup: LookUp(Business_Requirement_Document, 'Report Name'='Value- Report Name'.Text).ID},
If(
    Form1.Mode = FormMode.Edit &&  Text(Dup) <> DataCardValue2.Text ,
    true,
    false
))
#DataCardValue2 is the datacard bound to the item ID. YOu may need to add it, but it doesn't need to be visible.

 

If they change the Report Name to match any other entry then Dup will not match the ID for the current record, and it won't be null.  So when in Edit mode the label will show.  If they change it to be a unique value then Dup will be null and the error won't show.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Anonymous
Not applicable

Thanks!

Unfortunately, it did not work. With my earlier formula-
LookUp(Business_Requirement_Document, 'Report Name'='Value- Report Name'.Text, true) && (RH_SP_Form.Mode = FormMode.New)

It worked atleast when the form was in NEW mode, as described in my original question- now it does not work for both modes, NEW & EDIT

when I did this:

With({Dup: LookUp(Business_Requirement_Document, 'Report Name'='Value- Report Name'.Text).ID},
If(
RH_SP_Form.Mode = FormMode.Edit && Text(Dup) <> 'Value- Report Name'.Text ,
true,
false
))

With this formula, I do not see the error in green sectioned marked. Earlier, if upon hitting new somebody entered a Report name that already existed (as shown in orange)- even without hitting save the old formula was showing the error message in label that i have.

GauravG_1-1622731594728.png

And, if I open an existing SP list item to edit it, it by defaults shows the error- seems like it is still checking the name against itself.

GauravG_2-1622731647427.png

@Anonymous 
Change your visible formula to the following:

LookUp(Business_Requirement_Document, 'Report Name'='Value- Report Name'.Text, true) && ((RH_SP_Form.Mode = FormMode.New) || !(Parent.'Report Name' = 'Value- Report Name'.Text))

This will first lookup the record to determine if it exists.  If that is true, then it will be up to the form mode or the entered value not being the original value.

 

You do not need to duplicate true and false with an if condition for a true/false property.  It's just extra typing.

 

I hope this is helpful for you.

_____________________________________________________________________________________
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!

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 (863)