When using a Dataverse table, should I still use local collections?
I have a gallery which I want to patch items to and from and when using Dataverse directly, it is still a little slower than working on a local collection and then patching the gallery directly to the table in one go once editing has been completed.
What I don’t understand though is that when I first patch data to the collection shown in a gallery, to access the fields, I can use (for example) ThisItem.Start. However, when I patch the gallery to the Dataverse table and then reload this back into the collection for editing again in the same gallery, I have to use (for example) ThisItem.cr60e_start so it no longer shows in the gallery? How can I make sure the items are always shown whether directly from the collection first or after the collection has been patched to the Dataverse table and then back again to the collection? Do I need to use something like ThisItem.Start OR ThisItem.cr60e_start?
Many thanks.
Thanks but that doesn’t really help.
my main question is why when first patching to a collection can one patch to the column name and use column names in a gallery to show the fields. However when one then wants to reload the table back into the gallery, one has to use ThisItem.cr60e_columnname? I need to be able to show both in the same gallery. Many thanks.
Hi @jed76
Can you please check following link might be it helpful for you.
https://powerusers.microsoft.com/t5/Building-Power-Apps/Collection-to-Dataverse-Table/m-p/1677933
-------------------------------------------------------------------------------------------
Regards,
Bharti
Community Support Team _ Bharti
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
WarrenBelz
791
Most Valuable Professional
MS.Ragavendar
410
mmbr1606
275
Super User 2025 Season 1