cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MH5
Helper I
Helper I

Loading form if User().email has a record in SharePoint list

What I'm trying to achieve is similar to Solved: check if item exists if not create new using butto... - Power Platform Community (microsoft.... except I want this functionality upon loading the app, so without interaction of a button.

 

 

I have a SharePoint list that contains a large number of columns, I want to present the users of this list with a better experience so they can complete the form in multiple pages. The records contain a field that has the user's email address.

 

I'm trying to build an customized SharePoint form that has the following behavior:

If the user already has a record in the SharePoint list, then upon the form loading, load the existing record on the screen.

If the user does not already have a record in the SharePoint list, then upon the form loading, present the user with a new form.

The customized form should have 1 screen with 4 buttons which load different sections of the form.

MH5_0-1706828096673.png

Only the Profile section contains required fields, each section has a button to save the form that is loaded.

There are 4 forms, all connected to the same SharePoint list, upon saving the form, the next section is loaded with the next part of the form to be filled out. You can access any section at any stage if a record exists by using the navigation buttons on the left.

 

The OnVisible property of the screen currently has the below formulas:

 

Set(varSelectedRecord, Filter('Skills-Matrix', 'Email Address' = User().Email));

Set(varSelectedItem, First(varSelectedRecord));

Set(GallCount,CountRows(Filter('Skills-Matrix','Email Address'=User().Email)));

 

The first two formulas work fine in that I can use varSelectedItem as the value in the item property of the form that exists when "profile" is active, if a record already exists for the user, this record will be displayed in the form.

The formula for the GallCount variable presents me with a delegation warning for using CountRows.

 

I'm using GallCount to identify if the user already has an existing record. What I can't get to work is for the form to load as a blank form when GallCount = 0. What I've done so far to get around that is to create a second screen with a button that has 

 

If(GallCount=0,Navigate(Screen2),Navigate(Screen1);

 

Screen1 has the 4 button layout as included in the image above, and as previously mentioned will load up the existing record.

Screen2 has a new form that shows the relevant fields to complete the profile section of the form.

The behavior I want from the form on Screen2 is upon submission, to navigate to the Soft Skills section on Screen1 with the new record in the SharePoint list being the selected form item (which was created upon submission). However nothing is loading on the form in this section, it shows a blank form in edit mode instead.

 

The form in Screen2 has the below formulas for the OnSuccess property:

 

Set(varSelectedRecord, Filter('Skills-Matrix', 'Email Address' = User().Email));

Set(varSelectedItem, First(varSelectedRecord));

Set(GallCount,CountRows(Filter('Skills-Matrix','Email Address'=User().Email)));

Set(FormSection, 2);

Navigate(Screen1);  

 

What I'm looking for help with is:

  • How can I get the Custom SharePoint form to present the user with a form appropriate for their use scenario (existing record if record exists, new form if record does not exist) without using the new screen with a button? The objective is to get a form design with just a single screen where the user does not need to interact with anything except the form, the navigation buttons and the save buttons.
  • How can I avoid the delegation warning on the GallCount formula (the SharePoint list will exceed 2000 items), is there another way to identify if the user already has a pre-existing record in the SharePoint list?
  • How can I get the next sections to properly load the next form section when a new record has been created on Screen2? (it works fine when a record already existed on app launch)
  • Just as general feedback, it feels like what I'm trying to achieve should be simple, is there a more straightforward approach, am I making a silly mistake somewhere?
2 ACCEPTED SOLUTIONS

Accepted Solutions
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @MH5 ,'

Before I delve into any of the structure, the problem you are going to have is that an Integrated Form does not run OnStart or screen OnVisible (which is important to you here) on anything other than the first record selected (for example the user chooses another record it does not run) unless the browser is refreshed each time. Also multi-screen forms and Variables are problematic especially when you try to set things from the Integrated OnEdit / OnNew / OnView.
These problems do not exist in Canvas apps - is there any reason you are making an Integrated app with this complexity ? As an aside, you can fix the Delegation warning like this

With(
   {
      _Data:
      Filter(
         'Skills-Matrix',
         'Email Address' = User().Email
      )
   },
   Set(
      GallCount,
      CountRows(_Data)
   )
)

 

View solution in original post

MH5
Helper I
Helper I

To update my progress, I was able to resolve my issues by getting rid of the additional screens I had added when I was attempting to resolve the first issue.

The actions I've taken are as per below:

 

I removed the screen with buttons, there's just the 1 screen in the app.

I changed the OnStart property for the App to: (using @WarrenBelz 's fix for the delegation warning)

 

Set(varSelectedRecord,Filter('Skills-Matrix','Email Address'=User().Email));
Set(varSelectedItem,First(varSelectedRecord));
With({_Data:Filter('Skills-Matrix','Email Address'=User().Email)},Set(GallCount,CountRows(_Data)))
 
On the screen I changed the OnVisible to 
 
If(GallCount=0,NewForm(SharePointForm1));
Set(FormSection,1);
 
On the form itself, i changed the DefaultMode property to:

If(GallCount=1,FormMode.Edit,FormMode.New);
 
The buttons all have an appropriate OnSelect property where the Section var updates from 1 - 4
Set(FormSection,1)
The form inputs all have Visible properties that match the appropriate sections, for example FormSection =2
 
 
 

View solution in original post

4 REPLIES 4
WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @MH5 ,'

Before I delve into any of the structure, the problem you are going to have is that an Integrated Form does not run OnStart or screen OnVisible (which is important to you here) on anything other than the first record selected (for example the user chooses another record it does not run) unless the browser is refreshed each time. Also multi-screen forms and Variables are problematic especially when you try to set things from the Integrated OnEdit / OnNew / OnView.
These problems do not exist in Canvas apps - is there any reason you are making an Integrated app with this complexity ? As an aside, you can fix the Delegation warning like this

With(
   {
      _Data:
      Filter(
         'Skills-Matrix',
         'Email Address' = User().Email
      )
   },
   Set(
      GallCount,
      CountRows(_Data)
   )
)

 

Thanks @WarrenBelz ,

 

I've used your provided formula and there's no more delegation warning.

 

The reason I'm using the integrated form, and I might be misinformed here, is to avoid the PowerApps licensing costs per user. I usually make PowerApps within teams for the same reason.

I'm not using PowerApps for teams in this case as the request was to have it accessible through a SharePoint Community Page.

 

The intention is not to have multiple screens and not to provide users access to any records than their own. That's what I'm trying to achieve with these OnVisible formulas anyway. The idea is that a user loads the form (through direct link in webpart) if they never submitted a record before, they can create one. If they have created a record before, it would allow them to update this record with any required changes.

 

The 4 buttons for navigation do not navigate to other screens but rather make certain inputs in the form visible or not.

WarrenBelz
Most Valuable Professional
Most Valuable Professional

Hi @MH5 ,

I had a fairly good guess at your motivation and you are fortunate that the restrictions have been eased since these forms where introduced (initially unlicenced users could not even open them), however these forms were never designed to be full-blown apps, rather a replacement for the standard SharePoint new/edit/view and InfoPath forms.

As I mentioned, when the app is initially opened, then another record selected, the logic is that you have only changed the selected record, therefore the app does not re-open - it stays open (for performance reasons) and does not run OnStart or screen OnVisible. I noted some other things on my previous post that you will have difficulty with, particularly Variables and Collections that do not reset when you change records for the reasons I mentioned - the first one is going to cause you some issues here.

You may get some of this to work - the code you posted seems logical.

 

MH5
Helper I
Helper I

To update my progress, I was able to resolve my issues by getting rid of the additional screens I had added when I was attempting to resolve the first issue.

The actions I've taken are as per below:

 

I removed the screen with buttons, there's just the 1 screen in the app.

I changed the OnStart property for the App to: (using @WarrenBelz 's fix for the delegation warning)

 

Set(varSelectedRecord,Filter('Skills-Matrix','Email Address'=User().Email));
Set(varSelectedItem,First(varSelectedRecord));
With({_Data:Filter('Skills-Matrix','Email Address'=User().Email)},Set(GallCount,CountRows(_Data)))
 
On the screen I changed the OnVisible to 
 
If(GallCount=0,NewForm(SharePointForm1));
Set(FormSection,1);
 
On the form itself, i changed the DefaultMode property to:

If(GallCount=1,FormMode.Edit,FormMode.New);
 
The buttons all have an appropriate OnSelect property where the Section var updates from 1 - 4
Set(FormSection,1)
The form inputs all have Visible properties that match the appropriate sections, for example FormSection =2
 
 
 

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