My requirement is that when you select Parent combo box it should populate the dependent value combobox. Whenever we select a value in the Dependent Value Combobox, it reset after a few seconds, and the patching we do in the gallery reverts back to blank after a few seconds. It's not retaining the selected value in combo box.
We have two SP lists, one is to show the Combobox values in (dependent Value) and the second is to store the Parent and Dependent value combination.
On click of button "First time"
ClearCollect(collProductSalesReportPricing1,Filter(PH_SalesforceProductPricing,SalesForceRequestID=Blank()));
Create a blank collection of it.
On click of Add rows, we just add a new row with unique id.
Collect(
collProductSalesReportPricing1,
{
ID: If(
Last(collProductSalesReportPricing1).ID > 4000000,
Last(collProductSalesReportPricing1).ID + 1,
4000001
)
}
)
In Gallery, control
We have two comboboxes, cmbOperating and cmbProduct, and on Change event of both combox, we are calling Select(Parent);
In cmbOperating , "Items" has below code
Choices([@PH_SalesforceProductPricing]. 'Operating Segment')
DefaultSelectedItems event : ThisItem.'Operating Segment'
For cmbProduct Items:
For cmbProduct DefaultSelectedItems event:
And "On select" event of Gallery control, we are patching the collection whenever there is a change in these Combobox
Patch(
collProductSalesReportPricing1,
LookUp(
collProductSalesReportPricing1,
ID = ThisItem.ID
),
{
'Operating Segment' :cmbOperating.Selected ,
Product:cmbProduct.Selected.ProductHierarcnyDescriptionChild
}
);
Solved! Go to Solution.
Hi @rajeshrai1231 ,
I understand your structure a bit better now. Also (please remember to post code in Text) so watch spelling on the OCR'd code below. Firstly, it is fine patching each record as you do it, but a save button it probably better than OnSelect, which will trigger every time you click in the Gallery. That aside, your code (a small improvement below)
Patch(
collProductSalesReportPricingl,
{ID: ThisItem.ID},
{
'Operating Segment' : cmbOperating.Selected ,
'old Product Category':
11 + Len(cmbProduct.Selected.ProductHierarcnyDescriptionChild),
Product: cmbProduct.Selected.ProductHierarcnyDescriptionChild
}
)
is updating three fields, so if they are displayed in the gallery, the control displaying them needs to display the relevant item from the collection.
Now to your Combo Box - I firstly noticed a Delegation warning - this should be able to be removed with
With(
{
wPricing:
LookUp(
collProductSalesReportPricingl,
ID = ThisItem.ID
)
},
Filter(
PH_SAPHirerachyData,
'Product Hierarchy Description' = wPricing.'Operating Segment'.Value &&
ProductLevel = 2
)
)
but none of the above is the real issue here. I am assuming that the field able to be selected from the Combo Box is ProductHierarcnyDescriptionChild and that the field it is displaying from the data source is Product and this is a Single Line of Text - please confirm this. If all of the is correct, the DefaultSelectedItems of the Combo Box should be
{ProductHierarcnyDescriptionChild: ThisItem.Product}
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Visit my blog Practical Power Apps
@WarrenBelz You are awesome, I wasted almost 5 hours fixing the issue but you solved it in a few mins. Next time I will consider what I have learned here. I have accepted your solution.
I read that default selected items should be one of the rows that we have selected in the items of a Combobox, so I was again hitting the SP to get the same row. That was wrong. Thank's a lot.
Hi @rajeshrai1231 ,
The simple explanation for this is that all controls in a Galley reset wen any code is run from inside it, so the only path it to Patch the value selected to a field in the relevant record and Default to that field, so when the gallery resets, it will retain the value. If you are using a Collection for the Gallery Items, this is quite easily achieved OnChange of the control.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Visit my blog Practical Power Apps
Hi @WarrenBelz Thanks for the reply, if i understand correctly, the code which I am using in the "on select" event of Gallery, I should use in every control separately and not in the same place,
Patch(
collProductSalesReportPricing1,
LookUp(
collProductSalesReportPricing1,
ID = ThisItem.ID
),
{
'Operating Segment' :cmbOperating.Selected ,
Product:cmbProduct.Selected.ProductHierarcnyDescriptionChild
}
);
Now, i put the patch command separately for each control as given below
But still it's not retaining it's value. I weird point i forget to mentioned below: If i select the same value again twice then it worked perfectly.
e.g. if i select first-time "raj" then no value is selected, if I again select "Raj" then raj will retain theirs. If now i again select another value "Rob", it shows"raj" again but again if i select "Rob" then now it will change the value to "Rob"
This type of code, i have used in other projects too, but never encountered such an issue.
Hi @rajeshrai1231 ,
The critical thing is that the field in the collection that is displaying the value in the control needs to be updated to the new value and the Default of that control needs to be ThisItem.FieldName, so if you change 3 values, you need to patch all of them to the gallery record. I would be using OnChange (although OnSelect should work with a Combo Box). If you are only Patching the Combo Box, what are the Items and DefaultSelectedItems of this ?
HI @WarrenBelz
on change event of combobox, i m calling it's parent i.. gallery control
On Select, of the gallery, i am updating the collection for every item
Items property of Combobox, where I m using the previous combo box selected value to fetch a SP and populate a list
Default selected items property of Combobox, here depending on the selected product value, i am setting it.
Hi @rajeshrai1231 ,
I understand your structure a bit better now. Also (please remember to post code in Text) so watch spelling on the OCR'd code below. Firstly, it is fine patching each record as you do it, but a save button it probably better than OnSelect, which will trigger every time you click in the Gallery. That aside, your code (a small improvement below)
Patch(
collProductSalesReportPricingl,
{ID: ThisItem.ID},
{
'Operating Segment' : cmbOperating.Selected ,
'old Product Category':
11 + Len(cmbProduct.Selected.ProductHierarcnyDescriptionChild),
Product: cmbProduct.Selected.ProductHierarcnyDescriptionChild
}
)
is updating three fields, so if they are displayed in the gallery, the control displaying them needs to display the relevant item from the collection.
Now to your Combo Box - I firstly noticed a Delegation warning - this should be able to be removed with
With(
{
wPricing:
LookUp(
collProductSalesReportPricingl,
ID = ThisItem.ID
)
},
Filter(
PH_SAPHirerachyData,
'Product Hierarchy Description' = wPricing.'Operating Segment'.Value &&
ProductLevel = 2
)
)
but none of the above is the real issue here. I am assuming that the field able to be selected from the Combo Box is ProductHierarcnyDescriptionChild and that the field it is displaying from the data source is Product and this is a Single Line of Text - please confirm this. If all of the is correct, the DefaultSelectedItems of the Combo Box should be
{ProductHierarcnyDescriptionChild: ThisItem.Product}
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Visit my blog Practical Power Apps
@WarrenBelz You are awesome, I wasted almost 5 hours fixing the issue but you solved it in a few mins. Next time I will consider what I have learned here. I have accepted your solution.
I read that default selected items should be one of the rows that we have selected in the items of a Combobox, so I was again hitting the SP to get the same row. That was wrong. Thank's a lot.
@WarrenBelz I tried to solve that delegable issue, but even it's there with the new code
With(
{
wPricing:
LookUp(
collProductSalesReportPricing,
ID = ThisItem.ID
)
},
Filter(
PH_SAPHirerachyData,
'Product Hierarchy Description' = wPricing.'Operating Segment'.Value &&
ProductLevel = 2
)
)
Anything wrong i am doing here?
Thank @rajeshrai1231 ,
This blog of mine on Controls and their references may also be useful to you. Once you get your mind around the data structures inside these, you will wonder why it was difficult before.
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