cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

When going into edit form then delete the record that is in datacardvalue1

Hello,

I've entcountered the problem that I don't want to let users submit duplicate ID's of a record.

It works for new form, but not for edit form. Because when I open an item in the customized sharepoint form, and save it without 

even changing the records, the duplicate search via lookup function already regard this very entry as the duplicate. Even though I just open it for changing other records. On the other hand if I remove the duplicate search for the edit mode, then everybody can open a item a place a duplicate in the edit mode. That would be a huge loophole.

 

So I just thought of one solution: When I open an entry in edit mode, the OnEdit has to delete that ID, if I save it with the same ID everythin will be fine because the ID is deleted. In case I change to another ID it still will proceed to search for a duplicate:

 

I tried with many variations of Remove() but it didn't work out. Someone has an idea?

if ( Form.Mode= Edit.form...., then delete the ID from the record you just opened...

Thank you very much in advance. 

Best. 

 

1 ACCEPTED SOLUTION

Accepted Solutions

@Applicable88 ,

You simply need to change the LookUp to refer to Product, not ProductID and make sure it does not match the input field for that.

If(
   IsBlank(
      LookUp(
         ProductsTable; 
         Product=YourProductInput.Text
      )
   ) && SharePointForm1.Mode = FormMode.Edit;
   SubmitForm(SharePointForm1);
   Notify(
      "Duplicate Entry on Product " & YourProductInput.Text);
      Error
   )
)

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

View solution in original post

11 REPLIES 11

Hi, @WarrenBelz maybe you know a solution? Why a duplicate search lik :

 if (isblank(lookup(table, ID=DataCardValue1.Text) ; SubmitFrom(Sharepoint1); Notify ......Error)

will regard the ID in the edit customized sharepoint form as a duplicate? I cannot submit because the 

form regard the ID like a duplicate, even though I didn't change anything, I just click "edit" and right after without changing any records "save". 

 

 

I tried to add a Remove( ) commad in the OnEdit action, so that I can resave that entry again,  but nothing happens or I just jump right no the next item and then the item is lost, which isn't what I want. 

 

Best regards. 

 

 

HI @Applicable88 ,

If you are using SharePoint here, the ID is a unique number and is not re-used if deleted, so your test will always fail. If you are entering an ID in that text control and checking for its existence, then

 

If(
   IsBlank(
      Lookup(
         Table;
         ID = Value(DataCardValue1.Text)
      )
   ); 
   SubmitFrom(Sharepoint1); 
   Notify ......Error
)

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

@WarrenBelz thanks for the clarification. It was very  unfortunate that I use the colum "ID" as an example since apparently it is a automatic created identifier. The colum I'm talking about is actually a self created ProductID colum. In that case edit and duplicate check shouldn't work in edit form? But since the record is already as an entry in the datasource when I want to edit it, duplicate check confuse it's own  entry in edit mode as an duplicate and doesn't let me save it once opened. Deactivating duplicate lookup would mean that everybody could manually write as many duplicates in edit mode they want which is not the purpose of that customizer form. Is there any solution to this?

Hi @Applicable88 ,

If you are using a created value ProductID column, then you can certainly use

If(
   IsBlank(
      Lookup(
         Table;
         ProductID = DataCardValue1.Text
      )
   ); 
   SubmitFrom(Sharepoint1); 
   Notify ......Error

Also in SharePoint, you can "Enforce Unique Values" but if you do, also ensure there must be input or you cannot have two blank values

WarrenBelz_0-1653549373419.png

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

@WarrenBelz thank you very much for reminding that "enforce unique values" unfortunately in Sharepoint when using item-level permission you cannot force unique values in column. I do that so in my case user permission group can see everything and another only their own item inputs, so in case they can update their entries, if needed.

 

Yes as already in use I'm using that in OnNew when making new items :

If(
   IsBlank(
      Lookup(
         Table;
         ProductID = DataCardValue1.Text
      )
   ); 
   SubmitFrom(Sharepoint1); 
   Notify ......Error

 

But as I stated doing the same in OnEdit, it regards that entry which I selected for "Edit" in sharepoint as the duplicate value itself.

 

I'm doing the following:

In SharepointIntegration I'm setting global variables for OnNew and OnEdit

NewForm(SharePointForm1);; Set(Name;"NEW")

EditForm(SharePointForm1);;Set(Name;"EDIT")

 

In OnSave I have to deactivate the duplicate check for OnEdit otherwise I cannot save the entry after open it for editing:

If(IsBlank(LookUp(ProductsTable; ProductID=DataCardValue3.Text)) And Name="NEW" ;
SubmitForm(SharePointForm1);
If(!IsBlank(LookUp(ProductsTable; ProductID=DataCardValue3.Text)) And Name="EDIT" ;
SubmitForm(SharePointForm1);
Notify("ProductID is already on the list!";NotificationType.Error)));;

 

If I would reactivate duplicate check in Form Edit Mode (removing the exclamation sign), I woulnd't be able to save back the record and would get the duplicate Notifier:

 

If(IsBlank(LookUp(ProductsTable; ProductID=DataCardValue3.Text)) And Name="NEW" ;
SubmitForm(SharePointForm1);
If(IsBlank(LookUp(ProductsTable; ProductID=DataCardValue3.Text)) And Name="EDIT" ;
SubmitForm(SharePointForm1);
Notify("ProductID is already on the list!";NotificationType.Error)));;

 

Is there a way to still make duplication test in edit mode possible? 

 

The disadvantage with using "enforce uniqe values" is that I cannot use item - level permission. And second issue is that when I'm editing the ProductID in the form into a ProductID which is already on that SharePoint List it let me save the entry, but it automatically change the ProductID back to the number it was before open it for editing. There was no notification. 

Hi @Applicable88 ,

A couple of things - setting Variables with the built-in controls in integrated forms I have found to not have consistent controls. I tend to "keep it simple" if using integrated forms and reference SharePointIntegration.Selected whenever I need to refer to the current record or SharePointIntegration.SelectedListItemID for the ID of this. I also refer directly to the Form Modes

If(
   IsBlank(
      LookUp(
         ProductsTable; 
         ProductID=DataCardValue3.Text
      )
   ) && SharePointForm1.Mode = FormMode.Edit;
   SubmitForm(SharePointForm1);
   Notify(
      "Duplicate Entry on Product ID " & DataCardValue3.Text);
      Error
   )
)

You might see if this works for you.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

 

Hi @Applicable88 ,

A couple of things - setting Variables with the built-in controls in integrated forms I have found to not have consistent controls. I tend to "keep it simple" if using integrated forms and reference SharePointIntegration.Selected whenever I need to refer to the current record or SharePointIntegration.SelectedListItemID for the ID of this. I also refer directly to the Form Modes

If(
   IsBlank(
      LookUp(
         ProductsTable; 
         ProductID=DataCardValue3.Text
      )
   ) && SharePointForm1.Mode = FormMode.Edit;
   SubmitForm(SharePointForm1);
   Notify(
      "Duplicate Entry on Product ID " & DataCardValue3.Text);
      Error
   )
)

You might see if this works for you.

 

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

 

@WarrenBelz thats a great tip to write shorter without extra global variables, thank you.

 

Unfortunately it doesn't solve the problem of the duplicate search in the FormMode.Edit. It's really a 

mess that the lookup search consider the item that I just open for edit as the duplicate  and not letting me save the item. I tried to extend the syntax saying it should remove that record and submit, but of course it instead will jump to the next item. It would be easier, if that very item which is in FormMode.Edit is temporarily out of the datasource, but that might come with other dangers like losing data.

Hi @Applicable88 ,

I must admit I am a little lost here exactly what you are trying to do. The code I gave checks for duplicates and will not save if the current record has another "twin" in the data source. What is it exactly you are trying to achieve ?

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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

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

Top Solution Authors
Top Kudoed Authors
Users online (4,808)