Hello,
Hope you are all doing well.
I will ask a question that was asked several times. I read the other posts, tested and it doesn't work. So I guess there is something that i do wrong.
I'm trying to patch a lookup field.
I have a SharePoint list Process with fields Department ( lookup from List Department) and Process (Text field). These fields are part of a gallery (GalleryProcess). So I have GalDepartment and GalProcess.
And i have a SharePoint list called Department containing the name of the department in text fields.
My form is on list Process, I try to update my department. So I worte:
Patch(
Process,ThisItem, {
Process:GalProcess.Text,
Department: {
'@odata.type':"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
Id:GalleryProcess.Selected.ID,
Value:GalDepartment.Selected.Result
}
}
)
It patches the Process but doesn't patch the department.
Would someone be able to tell me what I'm doing wrong ?
Thanks a lot !!
I can unfortunately not make a screenshot of it cause it's on another computer where everything is restricted 😞
I try to do my best to explain but it's not easy.
My GalleryProcess is linked to my Process list. in this Process list i have 2 fields Peocess (text field) and Department (which is a lookup to Department list).
My GalleryProcess shows the content of the Process list (mainly my Process and Department fields).
My form is on the Process list, everything is done on the Process list.
I open my form, I create a new process setting the process name and department.. i save, ok . because this is part of my new form, i just use a "SubmitForm".
After the form is submited, my form remains open (i do this because all this is in fact a bigger form with tabs) and i see the GalleryProcess with the items from my Process list.
I want to update one of the processes, in the GalleryProcess, on the far right, i have a menu button that shows a cancel, edit, save and remove icon. I hit Edit...that allows my fields in the GalleryProcess to be edited...I do the modification... then i hit button save (which will set the current item back to disabled and save the new values to the Process list. This saves all my values but the department...(which is a lookup field link to the Department list)... doesn't get updated, it's just blank....
is it clearer ? I'm really sorry i can't explain it better 😞
No problem - you're doing fine explaining, it just takes a little longer to get a clear picture.
So, what is missing from your explanation though is another Gallery or some control called GalDepartment.
This is the source of your issue.
Trying to read back through the messages to put those pieces together - you referred to this as a dropdown in message #3. Is GalDepartment a dropdown control then?
You mention that the Items property is Distinct(Department, Department). Is there a reason you need to use distinct on that list? Are there duplicate departments?
aaaaahhh....
Yes, GalDepartment is the name of the fields Department (from Process list) in GalleryProcess for which i used a Dropdown control in GalleryProcess.
and yes there are duplicate departments (again, i try to make it simple but there are other fields in my lists. in Department list, there are department information fields as well as an entity and a division)
So if i correctly understand what you mean, I should add another gallery where the items come from Department list, hide this gallery and try to reference my GalDepartment field to the department field in that hidden gallery ? 🙂
Actually, I am more focused on your use of Distinct. If you are trying to have your lookup field in SharePoint lookup to a record in your Department list...then which one?? If there are, for example, 10 records that have "Sales" as the department and you use Distinct to filter out duplicates, then when you set your Lookup column in your list to a Department record...which one will be the one referenced in the lookup? - there are 10 of them!!
You don't need a hidden gallery or anything else special for this, but the above point on distinct is the one that is most concerning.
ok, i understand what you mean.
ok my bad, then just talking about Department and Process was not a good idea.
In my Department list , i also have fields like Entity, Division, Department comment
In my Process list, I have fields Entity, Division, Department, Process, Process comment
Entity and Division come from my first screen which holds basic information Entity, Divison, status, etc...
and i use global variables when swithing to the process screen in order to set the value or Entity and Division.
From that point on my Process form, I have those 2 values that are automatically populated and Department, which is a lookup field is a cascading drop down depending on the value of Entity and Division. So If i load a specific Entity/Division, I get the right Department.
so yes, there might be 10 of them but since that "couple" Entity-Division is unique, that gives me the correct Department.
So this is where you need to be...you need to have the Id of the Department record that corresponds to the correct record you want. Then, the Value of that record needs to be based on whatever you have defined it in your SharePoint list.
Once you derive that, then your formula is:
UpdateIf(
Process,
ID=ThisItem.ID,
{
Process:GalProcess.Text,
Department: {
Id: theExactDepartmentRecordID,
Value: theCorrespondingColumnValueAsDefinedInYourLookupColumn
}
}
)
ok....so.... UpdatIf can replace Patch (from my formula in the first post) but... ID and Value come from Department list , right ? or... no...ID is from Department and Value from Process?
my problem is still... how do i get these values ?
I add the Department list as a data source (which is already done) and ...? 😄
I'm so sorry i don't see the thing ..hmm
If the gallery has this selected you may not need the 'expanded' syntax.
Patch(
Process,ThisItem, {
Process:GalProcess.Text,
Department: GalDepartment.Selected
}
)
Thanks for you answer.
That's something i tried at the very beginning but it was not working. however it was not showing errors in my formula.... while now that i test it again... it shows errors saying it expects a Record value of different schema.
hmm...
Yes, UpdateIf is a better choice as it does not require two data actions and is more accurate. In your original formula, you were using ThisItem. This sometimes gives unpredictable results depending on the Items property of the Gallery, controls in the gallery, etc.
A lookup column needs to have the ID of the record that it is related to from the foreign list. In your case, it needs to be an ID from the Department list. The Value is determined by the configuration of the lookup column in SharePoint. Usually, the related lookup column is Title, but it can be anything. So, you need to provide the Value as the related column value in your foreign list.
So then - Yes - ID and Value come from Department list.
For example, if you have a record in Department that has "Sales" and is record ID 20, then your formula would be such as this:
UpdateIf(
Process,
ID=ThisItem.ID,
{
Process:GalProcess.Text,
Department: {
Id: 20,
Value: "Sales"
}
}
)
This just gives a "hard coded" example of what is needed.
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!
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
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.
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