cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
tagustin2020
Power Participant
Power Participant

Shipping Contents Collection Won't Write to SharePoint

@RandyHayes 

 

Hello Randy,

 

Me again! I'm trying to follow what you taught me in the Budget app I was working on as I have a similar use case with the Shipping App in the sense that I want to write the contents people wish to ship to a separate SharePoint list. I'm able to gather all of entries into the gallery as seen below, but I get errors when I try to write the Collection back to SharePoint via the Submit Form button. I've attached my screenshots and formulas in the Word doc (3 pgs). Would you mind taking a look and seeing if you can spot what I'm doing wrong? Thanks a mil, Teresa

 

SubmitFormSS.png

1 ACCEPTED SOLUTION

Accepted Solutions

@tagustin2020 

Not so much because the Created date (SharePoint column) will not be available at the point that you are doing the Collect to the datasource.

But, there is no reason you can't include that in the collected record.

i.e.

{Tile: tiItemDescription.Text,
     Value: tiValue.Text, //is this not a numeric also?? If so, Value(tiValue.Text)
     Quantity: Value(tiQty.Text),
     TotalValue: lblSubTotal.Text, //is this not a numeric also?? If so, Value(lblSubTotal.Text)
     Handling: ddHandling.Selected,
     UOM: tiUOM.Text,
     Year: Year(Now()),
     Quarter: RoundUp(Month(Now())/3, 0),
     Month: Month(Now())
    }

 

They would essentially reflect what was in the Created columns (once it is written).

 

_____________________________________________________________________________________
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

16 REPLIES 16

@tagustin2020 

The names of the columns of your Collection MUST match exactly to the Real name of the SharePoint list columns and, they must have the correct types in them.

 

I see in your collection definition that you have a "TotalValue" column, yet in your List definition, there appears to be a "Total Value" name.  If the real name of that column is "TotalValue" then you are fine, but I suspect not.

 

Also, for things like the Handling column - it is a choice column, yet you are setting it to a text value (ddHandling.Selected.Value)

If that dropdown items is Value based, then you can change the assignment of the value to ddHandling.Selected

If not, then set it to: {Value: ddHandling.Selected.Value}

 

Everything must match exactly!

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

@RandyHayes 

 

Hi Randy,

 

Here is a snapshot of my Collection columns. The internal name of my 'Total Value' SharePoint column is TotalValue.

 

Collection1ItemExample.png

The Items property of my dropdown is:

ValueTypeSS.png

 

Based on your guidance I changed the Collect formula for the Add button to this. I realized I was pointing to the wrong label for TotalValue so I fixed it.

Newaddbuttonss.png

 

A reset for the lblSubTotal.Text doesn't appear possible and shouldn't be necessary since it is based on a math formula (value * qty), right?

TV.HandlingChangess.png

Here are the label formulas in the gallery below input row.

CollectionTextss.png

My Collect formula is still not working. Wish I could spot what I am doing wrong. The problem has to be in either the Handling or the Value or TotalValue fields, right? I don't have any spaces in the internal names of my SharePoint columns so I haven't been able to spot the error yet.

Collect('Shipping Request Contents',colContents);

 

Thank you,

Teresa

 

@tagustin2020 

So, what is the exact error that you are getting from the formula at this point?

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

@RandyHayes 

 

Good morning Randy,

 

I've tried the formula in both the OnSelect of the SUBMIT FORM button and the OnSuccess property of frmMaster. I assume the latter is the correct place to write it as I want the contents to be connected to the req number that will be created once frmMaster is successfully submitted. 

 

frmMasterOnSuccessCollectError.png

 

When I saw the "Incompatible type" error message I double-checked my Quantity column in the SharePoint list and it is a Number type column. The format of the Text input field was set to Text so I changed it to Number, but it did not resolve the error. I'm not sure what to try next.

 

NewQtyNumber.png

 

I currently have 3 different ID types. The internal SharePoint ID, the 5-digit ID I am showing in the gallery since I don't have enough space for the long one, and the long ID I would like to record for the sake of reporting purposes (a separate screen I plan to build for the Logistics team).

 

ID-types.png

Here is the current OnSuccess formula for frmMaster:

Patch(FormPageStatus, {Page: CurrentPage.Page}, {Status: "Complete"});
UpdateContext({conFinalConf:true});
UpdateIf('Domestic Shipping Requests', ID=Self.LastSubmit.ID,{'Request Number': Self.LastSubmit.ID + 10000});
Collect('Shipping Request Contents',colContents)

 

The first line updates the progress tracker. The second line launches a confirmation pop-up with further instructions. The third updates the 5 digit ID. The Collect formula is the only piece not cooperating thus far.

 

ConfPopUpFS.png

 

Thanks for helping me Randy. I know you are busy with your own work so I really appreciate it - Teresa

@tagustin2020 

Yes, changing the format of a textinput control only changes the format of the control...not it's results.  The Textnput control only has a Text property to tell you what is in the control...and, as its name implies, it is Text.

So your plus formula should be:

Collect(colContents,
    {Tile: tiItemDescription.Text,
     Value: tiValue.Text, //is this not a numeric also?? If so, Value(tiValue.Text)
     Quantity: Value(tiQty.Text),
     TotalValue: lblSubTotal.Text, //is this not a numeric also?? If so, Value(lblSubTotal.Text)
     Handling: ddHandling.Selected,
     UOM: tiUOM.Text
    }
);
Reset(tiItemDescription); Reset(tiValue); Reset(tiQty); Reset(ddHandling); Reset(tiUOM)

If you get the correct column names and the correct datatypes in them, the collect function should work then in your OnSuccess action. 

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

@RandyHayes 

 

Hi Randy,

 

Sorry for the delay in response. I was inundated yesterday.

 

Thank you so much. Wrapping the Text inputs in the Value function made everything fall into place. I will document this for next time so I don't forget how to handle Number type columns. Obviously, it is core/basic concept that is important to understand if you want things to work properly.

 

I have a quick follow-up question. I don't have a date picker on the screen like I did for my budget app. Is there a way to leverage the internal Created SharePoint column to pick up the Year, Quarter and Month? The formula below of course doesn't work.

 

Year: Year(Created),
Quarter: RoundUp(Month(Created)/3,0),
Month: Month(Created)

 

Kind regards,

Teresa

 

Sorry to interrupt, I just notice a few things that might be helpful to you. 

 

1) You can use the now formula to capture the date without a date picker.  The formula would be Year(Now()). 

 

2) I'd suggest making an extra column called DateNum.  Generally, I do YearMonthDay the formula would be similar to Value(Year(Now())&If(Month>9,Month(Now(),0&Month(Now())&If(Day>9,Day(Now(),0&Day(Now())).  The reason you would want to do this is you can't do > or < for dates.  With a number value, you can use a date picker and convert it to a similar number format and then you can see everything greater than or less than that date.

 

3) When submitting fields, I generally like to submit fields in groups of 5.  It's really hard to figure out what went wrong when submitting 30-40 fields.  However, if you do it in groups of 5 it is easy to identify little things like a misplaced letter in your title or the field format is wrong.  After you know 5 is good, you add another 5 until you're all the way done.  

@dyee 

@RandyHayes 

 

Thank you for your input Dyee. I really appreciate how great everyone in the Community is about trying to  help out those who are stuck. I tried the Year:Year(Now()), but it didn't work for me whether I wrapped it in a Value formula or not (my SharePoint column is a Number type column). #3 is good advice. Shane Young talks a lot about taking "baby steps" as a way to approach formulas to make troubleshooting easier. I'm curious to see what Randy will have to say about #2 since he is pretty good at abbreviating formulas. 

 

Have a great day,

Teresa

@tagustin2020 

Not so much because the Created date (SharePoint column) will not be available at the point that you are doing the Collect to the datasource.

But, there is no reason you can't include that in the collected record.

i.e.

{Tile: tiItemDescription.Text,
     Value: tiValue.Text, //is this not a numeric also?? If so, Value(tiValue.Text)
     Quantity: Value(tiQty.Text),
     TotalValue: lblSubTotal.Text, //is this not a numeric also?? If so, Value(lblSubTotal.Text)
     Handling: ddHandling.Selected,
     UOM: tiUOM.Text,
     Year: Year(Now()),
     Quarter: RoundUp(Month(Now())/3, 0),
     Month: Month(Now())
    }

 

They would essentially reflect what was in the Created columns (once it is written).

 

_____________________________________________________________________________________
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

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