Ok, here is a simple thing I cannot get right:
For this, I'm doing:
Patch( ActionItems, ThisItem, { AssignedTo: cmbUsers.Selected } )
This is not working. Hovering the mouse over the formula above, I get 3 errors:
What I'm doing wrong? I've been fighting with this for quite some time now.
Appreciate any help 🙂
Hi @ArleiSilva ,
Could you please share more details about the formula within the Items property of the ComboBox?
On your side, I think it is not necessary to connect the ComboBox to your Users Entity, instead, you could consider connect to the LookUp field in your Custom Entity.
Set the Items property of the ComboBox to following:
Choices(Entity.LookUpFiled) /* Modify here on your side */
Best Regards,
Sik
Hi @v-siky-msft
First of all, thank you so much for your help with this. Here are the details:
Properties for the existing Combobox control (cmbUsers, connected to User entity):
Items: Users
DisplayFields: ["fullname","title"]
SearchFields: ["fullname","title"]
SelectMultiple: false
IsSearchable: true
I created a new Combobox control (MyNewComboBox) as suggested. Properties are below:
Items: Choices(ActionItems.AssignedTo)
DisplayFields: ["fullname","title"]
SearchFields: ["fullname","title"]
SelectMultiple: false
IsSearchable: true
Hello,
As shown in the image below, the limit of records that PowerApps can display from a CDS entity can be choosen in advenced params. However, it can not exceed 2000.
The only solution I have found for a similar case of mine consists in making an API which filters the 100k records according to a PowerApps trigger, all packed in a MS Flow.
Hi @PowerBrian
Thank you for your comments.
Yes, I'm aware of this limitation.
However, when using the Combobox connected to User entity, this limitation is not an issue since the connected data source gets requeried as I type. But the behavior is not the same when the combobox is connected to ActionItems.AssignedTo. I'm not sure why the behavior is different when consuming data directly from User entity versus consuming the same data through AssignedTo.
Is Flow the only option available? I would like to avoid this since it will certainly slow down execution thus negatively impacting the experience.
Thank you.
Hi @ArleiSilva,
Maybe your problem isn't with the ComboBox and the Lookup but rather with ThisItem from the Gallery.
As far as I remember, ThisItem from Galleries also includes the controls that you put in your template.
This allows you to write formulas that, for example, collect values from all TextBoxes in your gallery.
But the ThisItem schema won't be an exact fit to the schema of ActionItems.
And thus, it might not the right record for the second argument of Patch.
I might easily be wrong.
I am now assuming your custom entity to have a guid field named Guid, that you'll have to replace with your actual guid field name.
Can you try if the following works?
Patch(ActionItems, { Guid: ThisItem.Guid }, { AssignedTo: cmbUsers.Selected } )
Alternatively maybe
Patch(ActionItems, { Guid: ThisItem.Guid }, { AssignedTo: LookUp(Users, systemuserid=cmbUsers.Selected.systemuserid) } )
helps, using the same pattern of replacing a record that might not have the right schema with something that will have the right schema for sure.
Best of luck,
Sa.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.
User | Count |
---|---|
200 | |
52 | |
41 | |
39 | |
35 |
User | Count |
---|---|
261 | |
85 | |
71 | |
69 | |
66 |