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

Need to update value of a choice field based on whether people field is blank or not

Good morning everyone!

 

I have a form with the following:

  • A data card 'DC_AssignedTo', that contains a combo box 'CB_AssignedTo', which updates a people column in the SharePoint list.
  • A data card 'DC_Status', that contains a combo box 'CB_Status', which updates a choice column in the SharePoint list.

  I have the following code in the OnChange event of CB_AssignedTo:

 

 

// Store the value of CB_AssignedTo before the OnChange event
UpdateContext({
    PreviousAssignedTo: ThisItem.AssignedTo
});

// Store the value of CB_Status before the OnChange event
UpdateContext({
    PreviousStatus: ThisItem.Status
});

// OnChange event of CB_AssignedTo
If(
    IsBlank(PreviousAssignedTo) && !IsBlank(ThisItem.AssignedTo), // If CB_AssignedTo was blank before and now contains a value
    Patch(
       SRC, // Name of your SharePoint list
        ThisItem, // Patch the current item
        {
            Status: {Value: "In Progress", Result: "In Progress"} // Set the choice column to "In Progress"
        }
    ),
    If(
        !IsBlank(PreviousAssignedTo) && IsBlank(ThisItem.AssignedTo), // If CB_AssignedTo was not blank before and now is blank
        Patch(
            SRC, // Name of your SharePoint list
            ThisItem, // Patch the current item
            {
                Status: {Value: "Not Assigned", Result: "Not Assigned"} // Set the choice column to "Not Assigned"
            }
        )
    )
);

 

What I need to happen is as follows:

  •  If CB_AssignedTo was blank before the OnChange event, and now contains a value, set the value of CB_Status to "In Progress".
  • If CB_AssignedTo was not blank before the OnChange event, and now is not blank, do not change the value of CB_Status.
  • If CB_AssignedTo was not blank before the OnChange event, and now is blank, set the value of CB_Status to "Not Assigned".

Currently, this code is not changing the value of the Status field regardless of which of the three conditions above is true. Can anyone help me with this? Thank you!!

1 ACCEPTED SOLUTION

Accepted Solutions

@Nuke_It_Newport,

 

Thanks for the code snippet. The Office365Users API returns a record with a different schema, causing the error.

 

Since you are using SubmitForm, I think the best approach would be (1) adjusting the AssignedTo Datacard Update property to create the correct record schema & (2) prefilling the Status field based on the AssignedTo selection.

 

(1) AssignedTo Datacard Update property

If(
    !IsBlank(CB_AssignedTo.Selected),
    {
        DisplayName: CB_AssignedTo.Selected.DisplayName,
        Claims: "i:0#.f|membership|" & Lower(CB_AssignedTo.Selected.Mail),
        Department: "",
        Email: Lower(CB_AssignedTo.Selected.Mail),
        JobTitle: "",
        Picture: ""
    }
)

 

(2) Status combobox DefaultSelectedItems property

If(
    IsBlank(ThisItem.AssignedTo) && !IsBlank(CB_AssignedTo.Selected),
    {Value: "In Progress"},
    !IsBlank(ThisItem.AssignedTo) && IsBlank(CB_AssignedTo.Selected),
    {Value: "Not Assigned"},
    Parent.Default
)

 

With this approach the AssignedTo OnChange can be left blank and the Status Datacard Update property remains:

StatusCombobox.Selected

 

It is important to note that you would preferably set the status combobox displaymode to view. This would avoid users overwriting the prefilled status.

 

I hope this helps!

View solution in original post

10 REPLIES 10

Hi @Nuke_It_Newport,

 

The issue was caused due to the If condition checking the previous person value twice:

LaurensM_0-1708280674214.png

ThisItem.AssignedTo is evaluated twice - directly via ThisItem.AssignedTo and indirectly via the variable storing the same value. If you want to check the currently selected combobox value, we can use Self.Selected instead.

 

Additionally I have made some adjustments to improve readability & avoid code duplication:

 

// OnChange event of CB_AssignedTo
Patch(
    DATASOURCE, // Name of your SharePoint list
    ThisItem, // Patch the current item
    If(
        IsBlank(ThisItem.AssignedTo) && !IsBlank(Self.Selected), // If CB_AssignedTo was blank before and now contains a value
        {
            Status: {Value: "In Progress"},  // Set the choice column to "In Progress"
            AssignedTo: Self.Selected //Patch person column
        },
        !IsBlank(ThisItem.AssignedTo) && IsBlank(Self.Selected), // If CB_AssignedTo was not blank before and now is blank
        {
            Status: {Value: "Not Assigned"}, // Set the choice column to "Not Assigned"
            AssignedTo: Self.Selected //Patch person column
        }, //Else the status does not change & only patch the person column
        {
            AssignedTo: Self.Selected //Patch person column
        }
    )
)

 

Alternatively, you could also change the status during Form submission instead of a separate Patch during the Person combobox OnChange. This approach would require an adjustment in the Status DataCard Update property:

 

If(
    IsBlank(ThisItem.AssignedTo) && !IsBlank(CB_AssignedTo.Selected),
    {Value: "In Progress"},
    !IsBlank(ThisItem.AssignedTo) && IsBlank(CB_AssignedTo.Selected),
    {Value: "Not Assigned"},
    //Change to correct combobox name
    StatusCombobox.Selected
)

 

If this solves your question, would you be so kind as to accept it as a solution.
Thanks!

Thank you! When I implement your first solution, I get the following error:
"The function 'Patch has some invalid arguments.

Invalid argument type. Expecting  a Record value, but of a different schema.

Missing column. Your formula is missing a column 'Claims' with a type of 'Text'."

I'm going to try your second solution and see if that works for me.

I am still attempting to use your first code snippet. I should add, I have a button on the form, IC_SubmitFormButton, with the following code in the OnSelect property:

If(
   !EditForm.Error && 
    SubmitForm(EditForm),
    Navigate(SelectScreen, ScreenTransition.Fade)
);

With that, do I need to patch, or can I update the values for 'Status' and 'AssignedTo' on the form and then submit the form? Perhaps something like this? (I know this code isn't correct, but it's the closest I could come up with.

UpdateContext({
    SelectedUser: {
        DisplayName: CB_AssignedTo.Selected.DisplayName,
        Claims: "i:0#.f|membership|" & Lower(CB_AssignedTo.Selected.Mail),
        Department: "",
        Email: Lower(CB_AssignedTo.Selected.Mail),
        JobTitle: "",
        Picture: ""
    },
    StatusValue: If(
        IsBlank(ThisItem.AssignedTo) && !IsBlank(CB_AssignedTo.Selected),
        "In Progress",
        If(
            !IsBlank(ThisItem.AssignedTo) && IsBlank(CB_AssignedTo.Selected),
            "Not Assigned",
            ThisItem.Status
        )
    )
});

Hi @Nuke_It_Newport😊

 

Thanks for the additional info.

 

Using 'Self.Selected' in the first code block, we expect that the AssignedTo Items property has not been changed. In other words, the Items property should still be original Choices(Datasource.AssignedTo) which has the expected person record schema.

 

Would it be possible to share the AssignedTo combobox Items property.

 

Thanks!

Thank you. Here's the 'Assigned To' combo box Items property:

Office365Users.SearchUser(
    {
        searchTerm: CB_AssignedTo.SearchText,
        top: 5
    }
)

@Nuke_It_Newport,

 

Thanks for the code snippet. The Office365Users API returns a record with a different schema, causing the error.

 

Since you are using SubmitForm, I think the best approach would be (1) adjusting the AssignedTo Datacard Update property to create the correct record schema & (2) prefilling the Status field based on the AssignedTo selection.

 

(1) AssignedTo Datacard Update property

If(
    !IsBlank(CB_AssignedTo.Selected),
    {
        DisplayName: CB_AssignedTo.Selected.DisplayName,
        Claims: "i:0#.f|membership|" & Lower(CB_AssignedTo.Selected.Mail),
        Department: "",
        Email: Lower(CB_AssignedTo.Selected.Mail),
        JobTitle: "",
        Picture: ""
    }
)

 

(2) Status combobox DefaultSelectedItems property

If(
    IsBlank(ThisItem.AssignedTo) && !IsBlank(CB_AssignedTo.Selected),
    {Value: "In Progress"},
    !IsBlank(ThisItem.AssignedTo) && IsBlank(CB_AssignedTo.Selected),
    {Value: "Not Assigned"},
    Parent.Default
)

 

With this approach the AssignedTo OnChange can be left blank and the Status Datacard Update property remains:

StatusCombobox.Selected

 

It is important to note that you would preferably set the status combobox displaymode to view. This would avoid users overwriting the prefilled status.

 

I hope this helps!

Thank you. I've changed these properties. The following code throws a 'circular reference' error:

If(
    IsBlank(ThisItem.AssignedTo) && !IsBlank(CB_AssignedTo.Selected),
    {Value: "In Progress"},
    !IsBlank(ThisItem.AssignedTo) && IsBlank(CB_AssignedTo.Selected),
    {Value: "Not Assigned"},
    Parent.Default
)

Any ideas how to correct this?

I can set the status combobox displaymode to view. There's a third choice for this field of "Completed". The end user will populate the form, and when they submit the form, I will need to automatically change the status to "Completed" and set the current time and date on the field SRCCompDate.

 

@Nuke_It_Newport 

 

The circular reference may be caused due to other code within your form, normally the error will guide you to the circular reference. Could you share the exact error message?

 

With the current code, the combobox will be prefilled with either status and that respective status will be patched to the Datasource. The data will only be saved once the Form is submitted - does this mean the status should always be set to 'Completed' when submitting the Form?

 

If this is correct, why are the other statuses needed since the data is only saved on form submission? (As I understand it currently: the other statuses will never exist in your list)

Thanks for your help, and your patience! I am still deciding how the end user will interact with the app and the edit form. My thoughts are as follows: The end user selects the record, which will initially have a status of "Not Assigned", then navigates to the edit form. The user assigns the record to themself with the field "AssignedTo". When this action happens, the status is set to "In Progress". There may be a period of days before the user completes the form. Once the user completes the form and acknowledges completion of the form through some method such as a checkbox control, then clicks the "Submit Form" button, the field "SRCCompDate" will populate with the current date and time, and the "Status" field will be set to "Completed".

I've attached screenshots of the code that is throwing the error, as well as the error message.

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