cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ToubleShoot123
Frequent Visitor

Network Error while using Patch function: Field is Required (In Forall over gallery)

Hello everybody,

I've stumbled over a really odd problem when trying to create an editable table using containers and a gallery.

In this editable table I have a dropdown box. It gets its values from a SQL Table that basically serves as an ENUM.

So for the settings of the Dropdown:

 

 

Items = FieldTypes //(this is a connected table)

Default = LookUp(FieldTypes; ID = ThisItem.FieldType).Name
//The gallery this dropdown is in contains a Column called FieldType that is an integer/ID

 

 

 

There is also a button, that once activated does the following:

 

 

 

ForAll(
        gal_Table_Columns.AllItems;
        Patch(
            ReferencedObjectColumns;
            ThisRecord;
            {
                ...
                FieldType: drp_Table_FieldType.Selected.ID;
                ... //A similar snippet works fine for TextInputs or Toggles
            }
        )
)

 

 

 This oddly enough throws the error in the title. Hovering over the Code snippet say the value is null.

Even stranger things happen when I add the following snippet to the DropDown OnChange Method:

 

 

OnChange = Patch(ReferencedObjectColumns; ThisItem; { FieldType: drp_Table_FieldType.Selected.ID })

 

 

Not only does it properly Patch the Data, if you change the Field but it also makes the error of the "SaveAll Button" disappear even if you don't change anything in the data.

 

Maybe somebody has a clue in this regard, as this seems like quite unexpected behaviour to me. 

 

8 REPLIES 8
v-jefferni
Community Support
Community Support

Hi @ToubleShoot123 ,

 

In Patch function, the second parameter should be one of the records that belongs to the table of first parameter. In you case, ThisItem is apparently from Gallery.AllItems, which is not the same data source as Patch function. 

 

I assume Items of Gallery is TableA, source table to Patch is TableB, to update existing items in Table B based on Gallery:

ForAll(Gallery.AllItems, Patch(TableB, LookUp(TableB, criter that find the record in Table B), {TabelBColumn1:..., TabelBColumn2:..., TabelBColumn3:..., TabelBColumn4:...}))

 

to create new entries in Table B:

ForAll(Gallery.AllItems, Patch(TableB, Defaults(TableB), {TabelBColumn1:..., TabelBColumn2:..., TabelBColumn3:..., TabelBColumn4:...}))

 

Best regards,

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

ToubleShoot123
Frequent Visitor

Hi @v-jefferni 

 

I actually want to Patch TableA (the one where the items of the gallery come from)

This works great for all non-dropdown fields.

 

However for the dropdown we had to take the Items from another table (since the SQL Server TableA does not support Enums and we needed a secondary table for the categories.

 

In other places the way I've proceeded works fine this way:

- Dropdowns in a Form Submit just fine by giving the correct formula to the Update Property of the Datacard.

- Dropdowns in a Galery (without a datacard) patch just fine when using OnChange.

 

It just does not work in the ForAll Patch context. 

Basically we don't want to Patch TableB. We want to Patch Table A. Table B's only purpose is to provide the valid categories for the dropdown (linked to Table A by an ID).

 

Hi @ToubleShoot123 ,

 

So, the requirement is to bulk update items in the Gallery? Please try:

ForAll(
        gal_Table_Columns.AllItems As GA;
        Patch(
            ReferencedObjectColumns;
            LookUp(ReferencedObjectColumns; ID = GA.ID);
            {
                ...
                FieldType: GA.drp_Table_FieldType.Selected.ID;
            }
        )
)

 

Best regards,

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Hi @v-jefferni 

 

This sadly creates the very same error message. It might be aquivalent to what I tried before.

Hi @ToubleShoot123 ,

 

It seems like caused by the connector, which exact data source are you using?

 

Best regards,

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

Hi @v-jefferni 

 

Sorry for the late answer, I am on vacation for now but will also try to Check into this thread from time to time.

 

The Database should be a Microsoft SQL Server. I will be able to double Check at the start of January.

 

Thanks for the help so far and I wish you happy holidays!

Hi @ToubleShoot123 ,

 

Using Patch to edit SQL server records requires the primary key value. So, please try the formula below:

ForAll(
        gal_Table_Columns.AllItems As GA;
        Patch(
            ReferencedObjectColumns;
            {FieldType: GA.drp_Table_FieldType.Selected.ID);
            {
                ...
            }
        )
)

 

Best regards,

Community Support Team _ Jeffer Ni

If this post helps, then please consider Accept it as the solution to help the other members find it.

ToubleShoot123
Frequent Visitor

Happy New Year @v-jefferni ,

I don't think this is quite the solution.

 

It tosses the very same error. Also I don't really understand how you can pull out the Field to set from the remaining fields and put it where in the Patch you would usually require a specific Record/Entry.

Or is it that you are suggesting to Patch the entries where the primary ID matches that of the Fieldtype Column?


That however would be bad, since the FieldType Table only has 3 entries. I wll try to make it very clear what we are doing here, as I feel I have not really managed to convey what I want to achieve here.


This is the SQL table behind ReferencedObjectColumns:

IDColumnNameDataTypeFieldType......
1"Savings""int"1  
2"Costs""in"2  
3"Description""nvarchar"1  

Here FieldType is just the primary ID of another table.

IDName
1"Dimension"
2"Fact"
3"Key"

Having this additional table allows easily taking care of the values required for the dropdown. In SQL erms we would also join these two tables together whenever required.

When we use the ForAll Patch Command we want to patch the ReferencedObjectColumns Table.
For fields like "ColumnName" which are filled using just a textInput, this works even with the Initial method described in my very first post.

 

The only place this makes a problem ist when trying to Patch from a dropdown Box that got its values from the FieldTypes Table. This feels like it should not be so difficult and in fact just using Patch in the OnChange method of the Dropdown works perfectly fine, but this is proving a headache.

BTW just to confirm again. It's a Microsoft SQL Server. Just checked it.

 

While we aren't really moving forward, I still want to thank you for your help attempts. Maybe we will figure it out.

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