As the title mentioned im trying to select the item in my combi box which is connected with my sql data if the user press a button.
I already know they are not really working OnClick events to adress something else. So Im trying to work with UpdateContext.
My Button OnClick/Select Event:
If(
FilterModus = true;
Set (
Item1;
{
_Type: ComboBox1_3.Selected.Result;
_Manufacturer: ComboBox1_7.Selected.Result;
_Description1: ComboBox1_8.Selected.Result;
_Description2: ComboBox1_9.Selected.Result
}
);
UpdateContext({ButtonPressed1: true})
)
I thought im going to get the selected Item with the Default Property of the Combobox itself.
If(
ButtonPressed1 = true & FilterModus = false;
First(
Filter(
'[dbo].[Devices]';
Text(Item1._Type) in Type
).Type
);;
UpdateContext({ButtonPressed1: false})
)
But like this nothing happens. My Record variable Item1 has values though.
Solved! Go to Solution.
separately
If(
ButtonPressed1 = true && FilterModus = false;
First(
Filter(
'[dbo].[Devices]';
Text(Item1._Type) in Type
).Type
))
It works. Also the if case is not the problem at all.
So the three pieces are not the problem but only if the are handled together. But this exatly what I need.
here is a little Screenshot of my current ui. the first goal of the ui is to do the flow as fast as possible.
Thats why I want to add something like favorites
I really need to distinct my data first because of duplicates. is there an other way to delegate my data with a distinct syntax ?
And with button trigger it should autoselect the item. thats why I thought I should use First Function
Thanks @Macwin ,
How many Types do you have and are they relatively static?
You can get around this one if this is the case by reference lists. You can then simply query these - more than 50% of my choice fields are collected and/or filtered from these.
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.
the number of devices types or devices at all are not settled. And since the Device table is going to be handled like a catalogue I really need to use something like distinct for handling duplicates. The Device Table is flat. For example
Notebook | Lenovo | XYZ1 |
Notebook | Lenovo | XYZ2 |
Notebook | Lenovo | XYZ3 |
Output in PowerApps is
Combobox Items : Type -> Notebook
Combobox Items : Manufactuer -> Lenovo
Combobox Items : Description -> {XYZ1; XYZ2; XYZ3}
Its like a nested filtersystem 🙂
This is already working without the favorite feature I want to implement.
This is how it works (its just the favorite function without distinct method)
And this is the way an user can select the device without using favorite button
So everything works except if the are used together 😞
Thanks @Macwin ,
I have answered a couple of posts on triple filters - it is good to see you have it totally under control.
The types are easy can Collect these hard-coded
ClearCollect(
colType,
{
Type:Laptop
Type:Notebook
Type:Monitor
. . . . . .
}
)
or you could collect them from a reference list
ClearCollect(
colType,
TypeList //this being the table name with Type as the only field
)
Your dropdown Items would in both cases would be colType.Type
Manufacturer would probably be the same (particularly the reference list)
Now for ongoing management of the reference lists, it is easy after any new item is entered to check if is exists on the list and it not Patch a new record.
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.
But how does this collection system affect my problem with saving & loading the specific record as optional possibilty ?
//Saving current values
ClearCollect(
Item1;
{
_Type: ComboBox1_3.Selected.Result;
_Manufacturer: ComboBox1_7.Selected.Result;
_Description1: ComboBox1_8.Selected.Result;
_Description2: ComboBox1_9.Selected.Result
}
Hi @Macwin ,
I was saying only do collections for the ComboBox/DropDown values - about 80% of mine are done that way and most off reference lists, which are self-managed as described in my last post.
The Manufacturer is easy as there will be no duplicates. The Type would need some thought, but could include a second column for Manufacturer to give all the combinations. If you do this, you do not need the first list as after collecting, it would then be easy to do both distinct queries. Also you simply write new records when an item is entered that is not on the list. You then do not have to worry about complex filters as all queries work on collections.
This is only one solution option, but I am familiar with it and it works.
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.
Oh Pardon me. I forgot to mention. Im writing/patching this Values (Only the deviceID) as referential foreign key into another table.
But I like the idea to manage this with collections since there are not any traffic perfomance problems. But I already know Collections are not fully supported using it in Forms components.
Could you be more specific with "The Manufacturer is easy as there will be no duplicates." Why are there no duplicates in collections ?
By the way I dont get any delegate warnings using Distinct Method
For example ->
Distinct(Filter('[dbo].[Devices]';ComboBox1_3.Selected.Result in Type).Manufacturer;Manufacturer)
I will try it with the collection and maybe my Error with loading specific variable/collection (Item1) is solved 🙂
Hi @Macwin ,
I am a SharePoint user, so I can only go off MS documentation (which I have found in the past to be not totally up to date)
If you do not have delegation issues with Distinct or In, then collections only represent a performance improvement (but a good one).
With my duplicate comment, imagine Manufacturers as you would in a normalised data set - you have a table with one record for each (and their static details) and reference it when required. I have lists the same and collect the fields I need for DropDowns/ComboBoxes (and use Lookups to get other data from it).
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.
I made it working with Collection but I still cant load the selected Value which is saved as variable (Im using only the ID now as reference) to my comboxes :S
It only works without distinct
If(
ButtonPressed1 = true And FilterModus = false;
Filter(
DeviceList;
Id = Item1
).Type;
DeviceList.Type
)
Else case must something like Distinct
I dont get it working with Distinct 😞
Its working 🎉
Item Syntax from Combobox
Distinct(
If(
ButtonPressed1 = true And FilterModus = false;
Filter(
DeviceList;
Id = Item1
).Type;
DeviceList.Type
);
Type
).Result
Select Item Syntax on Button Triggered
Comboxbox Property DefaultSelectedItems
First(
Distinct(
If(
ButtonPressed1 = true And FilterModus = false;
Filter(
DeviceList;
Id = Item1
).Type;
Blank()
);
Type
).Result
)
Its kinda dirty and Im sure there is better way to implement this feature.
Anyway this problem did cost some time and Im fine with this solution at the moment 🙂
Thanks again @WarrenBelz for your big help. Wouldnt solve it without your tips
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