cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
sthota
Helper III
Helper III

Unable to Patch Status Default Choice Column into Dataverse Table

We have a requirement to import the data from one entity to another within the same environment. We are trying to use ForAll with a Patch statement as follows.

//Inside ForAll -> Patch Statement code
Status: If(
                CollectionCreatedOutOfSourceTable.Status = 'Status (SourceTable)'.Open,
                'Status (TargetTable)'.Open,
                'Status (TargetTable)'.Closed
           )

We do not see any syntax error with the above piece of code. However, we are getting the following runtime error.

statecode: the specified column is generated by server and cannot be specified


We are getting various errors such as expecting an option set value or default schema has been changed when we try to modify the code. FYI, the Status column has the same data type and the same set of choices such as Open/Closed in both the source and target tables

 

If we remove the Status column from the patch statement then it just seems to work fine.

FYI, we do not have any issues patching the default status column inside the target table in the new app.

Thank you!!

1 ACCEPTED SOLUTION

Accepted Solutions

Hey,

So Ive made a little test and it seems you cannot add Inactive record, but you can deactivate it after:

When creating record:

Z_Lukowski_1-1633642360647.png

 

 

When updating existing record:

Z_Lukowski_0-1633642296733.png

So basicly you need to create records first and then deactivate them, after Initial Patch you need to find your newly created records (I dont know the condition you have with initial Patch), but it will be something like this:

ForAll(yourCollectionName As TempName, If(TempName.Status( 'Source Table')= 

. Closed, Patch(NameofDestinationTable, ID = TempName.ID, {Status: Status('Target Table').Closed}))

 

Or you can Create New collection with Filter based on status and if you have GUID, you can go bananas and use Function Patch(NameOfDestinationTable, YourFilteredCollectionName) - 

 

View solution in original post

6 REPLIES 6

Hello,

So I think I know where the problem can be hidden,

Check the dataverse if you don't have 2x Status field because there is a "status" field that is generated by the system and it cannot be changed, and you may have the custom one created in your table, they both can have the same name, 

simple example which I've created on my table:

Z_Lukowski_0-1633636055857.png

Hope that helps,

BR

Zbigniew

Hello @Z_Lukowski ,

Thank you so much for your prompt response. As you mentioned, we are using the default Status column i.e. statecode as highlighted above in the screenshot, and changed the options from Active/InActive to Open/Closed. However, we did the same thing in the source table as well as in the destination table and we could get it to work without any issues so far. We did patch around those in our application too. We are having this issue only when we are trying to migrate from one table to another. 

I believe you're right here. I could recollect trying to create a new record into the Dataverse table using an Edit form and patch the Status column into the table as Active/InAcive once at the time of record creation, but we couldn't do that, as it expects always an Active Record into the table. It doesn't even accept the Status column into the Patch statement, even though we would like to patch Active status.

Probably, we can import all-new records as default open records into the target table then update as closed for the closed records (or) a new Status field a custom column into the table as you recommended

Thanks,
Srinivas

Hey,

So Ive made a little test and it seems you cannot add Inactive record, but you can deactivate it after:

When creating record:

Z_Lukowski_1-1633642360647.png

 

 

When updating existing record:

Z_Lukowski_0-1633642296733.png

So basicly you need to create records first and then deactivate them, after Initial Patch you need to find your newly created records (I dont know the condition you have with initial Patch), but it will be something like this:

ForAll(yourCollectionName As TempName, If(TempName.Status( 'Source Table')= 

. Closed, Patch(NameofDestinationTable, ID = TempName.ID, {Status: Status('Target Table').Closed}))

 

Or you can Create New collection with Filter based on status and if you have GUID, you can go bananas and use Function Patch(NameOfDestinationTable, YourFilteredCollectionName) - 

 

@Z_Lukowski It helped us attain the solution in two steps as mentioned above.
1. First import all records as Open.

2. Update Closed records in the old table to Closed Status in the new table using below

// Update imported closed records to status Closed into new table
ForAll(
    // Filtering closed records in the old table
    Filter(
        OldTable,
        Status = 'Status (OldTable)'.Closed
    ) As colOldClosedTableName,
    // Checking the condition
    UpdateIf(
        NewTable,
        'Table Unique ID' = colOldClosedTableName.'Table Unique ID',
        {Status: 'Status (NewTable)'.Closed}
    )
);

Thanks !!

@sthota  - Thank you, remember also that UpdateIf Function is not delegable, by default it will only change status of 500 records, you can set it in canvas app up to 2000 but thats it, you cannot use it beyond that number, if number of record exceeds 2000, you need to use Patch or set more restrictive filters,

 

BR 

Zbigniew

Thanks for reminding us @Z_Lukowski about the delegable issue with UpdateIf. This is a one-time activity and the closed records are below the thousand mark, so it should work with the settings change as you mentioned above.

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