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

Combox Default Select Items not writing to SharePoint on form submission

I'm writing a canvas app with a multi-tabbed Wizard to guide users on the information I want to extract from them, in a user-friendly way.

The last tab of the wizard is a Summary page, which I've setup as a New Form which collects the data from the various tabs of the Wizard using DefaultSelectedItems property to grab the different values. I then simply submit this New Form to  write to my SharePoint List backend. Everything is writing to SharePoint successfully except for one column which is for selecting one or more reasons for something from a list.  In my SharePoint List, the problematic column is a multiselect from a Lookup of another SharePoint list, where we pull through the Title property.

In my Wizard to capture the information, I have a small gallery with check boxes where users can simply check the one or more boxes that apply.

The OnCheck property is using this syntax to write the values to a Collection: 

 

 

Collect(colReason,{Value:ThisItem.Title})

 

 

Likewise the OnUncheck property is using similar syntax to remove the values from the Collection:

 

 

Remove(colReason,{Value:ThisItem.Title})

 

 

 All good and the collection colReason creates a table with the Value containing the text selected by the user.

 

On my Summary page's New Form, I've imported the Reason field for the SharePoint list I'm writing to.

The ComboBox has the imported value for Items property like:

 

 

Choices([@'My SharePoint List'].Reason)

 

 

In order to populate the items the user selected within the Wizard I'm using the DefaultSelectedItems property like this:

 

 

{Value:colReason.Value}.Value

 

 

Data type: Table is reported and the Value in the table does indeed contain the selected items on different rows.

Everything is readable in the ComboBox on the New Form, and if I have the ComboBox in DisplayMode=Edit then you can see it has selected the items.

My problem is when I then Submit the New Form, the Reason selections simply aren't being written to SharePoint column. The annoying thing is, with the same syntax in place, if I de-select the items that were default selected, and then manually re-select them, then when I Submit the New Form it will write the data! 

I'm tried various other syntax which was accepted and displayed the values in the New Form but had the same issue of not writing to SharePoint. I've tried other workarounds like a separate ComboBox in the same card to pull the values from the collection, then select the DefaultSelectedItems of the original ComboBox to pull from the new ComboBox... but still the same problem. I even tried to Patch the values separately like this, but to no avail:

 

 

Patch('My SharePoint List',LookUp('My SharePoint List', 'ID' =NewForm.LastSubmit.'ID'), {Reason: DataCardValue180.SelectedItems});

 

 

 I'd be ever so grateful if someone could please help here! Surely there must be an answer to this problem? 

 Thanks all!                        

1 ACCEPTED SOLUTION

Accepted Solutions

After a bit more research on other forums and a bit more experimentation I've found the solution. I'm posting my solution here, in the hope it might help someone else in the future!

 

First thing I've changed is the Gallery with checkboxes where the users were selecting their Reasons. Instead of this Gallery's Items property set to pull the Reason (Title) value directly off the lookup SharePoint list (Reason), I'm pulling that entire SharePoint list into a  new Collection called colReasonList in my App's StartUp with not only the Reason description (Title), but also crucially with its original ID (ID). 

 

ClearCollect(colReasonList, ShowColumns(Reason,"ID", "Title"));

 

Modification of the OnCheck property for the checkbox in the gallery now is:

 

Collect(colReason,{Value:ThisItem.Title, Iterator:ThisItem.ID})

 

Modification of the OnUnCheck property for the checkbox in the gallery now is:

 

Remove(colReason,{Value:ThisItem.Title, Iterator:ThisItem.ID})

 

This takes just the required selected entries out of the colReasonList collection and puts them into a new collection called colReason - with the Value being the Reason Description (Title) and the original ID now being an Iterator field.

 

Meanwhile, in my Wizard's summary page, that form does have the Reason box in DisplayMode view with DefaultSelectedItems just displaying the selected reasons still using 

 

{Value:colReason.Value}.Value

 

  - although this doesn't write to SharePoint as part of the form submission it's needed just so the user can read his summary.

 

The writing to SharePoint I handle not through Form submission, rather through patching in a multistep approach:

Step 1 - create a new Collection called colReasonTable with special formatting for patching to SharePoint, based on values written temporarily to the Collection colReason upon selection in the Gallery:

 

Clear(colReasonTable);
ForAll(
    colReason,
    Collect(
        colReasonTable,
        {
            '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderReference",
            Id: Iterator,
            Value: Value
        }
    )
);

 

Note this takes the Iterator which was the original ID from the SharePoint lookup list via the initial Collection, and puts it as an ID value for the final collection ready for patching. If you don't have the correct ID from the original SharePoint LookUp column's SharePoint list then it will not write the correct data when you patch, rather will patch a different Title value from the SharePoint LookUp list!

Step 2 - Patch to the SharePoint List the Reason selection(s) after the main Summary form is submitted.

In the OnSuccess properties of my Summary Form I have a patch command:

 

Patch('My SharePoint List', LookUp('My SharePoint List','ID' = varLastID), {Reason: colReasonTable});

 

(Note I set a variable for the ID just written to by the Form in my SharePoint list using 

 

Set(varLastID, WizardNewForm.LastSubmit.ID);

 

but this I suppose is optional - I needed it because I was doing various other functions with the same ID and it was easier to save the value as a variable for those purposes).

View solution in original post

1 REPLY 1

After a bit more research on other forums and a bit more experimentation I've found the solution. I'm posting my solution here, in the hope it might help someone else in the future!

 

First thing I've changed is the Gallery with checkboxes where the users were selecting their Reasons. Instead of this Gallery's Items property set to pull the Reason (Title) value directly off the lookup SharePoint list (Reason), I'm pulling that entire SharePoint list into a  new Collection called colReasonList in my App's StartUp with not only the Reason description (Title), but also crucially with its original ID (ID). 

 

ClearCollect(colReasonList, ShowColumns(Reason,"ID", "Title"));

 

Modification of the OnCheck property for the checkbox in the gallery now is:

 

Collect(colReason,{Value:ThisItem.Title, Iterator:ThisItem.ID})

 

Modification of the OnUnCheck property for the checkbox in the gallery now is:

 

Remove(colReason,{Value:ThisItem.Title, Iterator:ThisItem.ID})

 

This takes just the required selected entries out of the colReasonList collection and puts them into a new collection called colReason - with the Value being the Reason Description (Title) and the original ID now being an Iterator field.

 

Meanwhile, in my Wizard's summary page, that form does have the Reason box in DisplayMode view with DefaultSelectedItems just displaying the selected reasons still using 

 

{Value:colReason.Value}.Value

 

  - although this doesn't write to SharePoint as part of the form submission it's needed just so the user can read his summary.

 

The writing to SharePoint I handle not through Form submission, rather through patching in a multistep approach:

Step 1 - create a new Collection called colReasonTable with special formatting for patching to SharePoint, based on values written temporarily to the Collection colReason upon selection in the Gallery:

 

Clear(colReasonTable);
ForAll(
    colReason,
    Collect(
        colReasonTable,
        {
            '@odata.type': "#Microsoft.Azure.Connectors.SharePoint.SPListExpanderReference",
            Id: Iterator,
            Value: Value
        }
    )
);

 

Note this takes the Iterator which was the original ID from the SharePoint lookup list via the initial Collection, and puts it as an ID value for the final collection ready for patching. If you don't have the correct ID from the original SharePoint LookUp column's SharePoint list then it will not write the correct data when you patch, rather will patch a different Title value from the SharePoint LookUp list!

Step 2 - Patch to the SharePoint List the Reason selection(s) after the main Summary form is submitted.

In the OnSuccess properties of my Summary Form I have a patch command:

 

Patch('My SharePoint List', LookUp('My SharePoint List','ID' = varLastID), {Reason: colReasonTable});

 

(Note I set a variable for the ID just written to by the Form in my SharePoint list using 

 

Set(varLastID, WizardNewForm.LastSubmit.ID);

 

but this I suppose is optional - I needed it because I was doing various other functions with the same ID and it was easier to save the value as a variable for those purposes).

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 (1,334)