You’re offline. This is a read only version of the page.
83
The great post Dataverse is not a database sets forth how Dataverse is distinguished from an RDBMS, such as SQL Server. The follow-on comment addresses Dataverse's limitations on joins traversing multiple tables.
Since this is a frequent business requirement in complex applications, is there a current recommended best practice for handling it with Dataverse, or if one has this business requirements, is that sufficient reason to conclude that Dataverse is not well suited for the requirement ?
Here is an example scenario:
Hypothetical tables
Use case
"Query a list of ingredients needed to make any of Ann's favorite drinks"
This scenario presents all the time in our business requirements.
(Thanks to @ChrisPiasecki for helping me get started with this yesterday.)
Hi @Chris1969
One method for complex queries across multiple tables in Dataverse is to use FetchXML. However, this depends on where you want to query the data from and how you want to use it. Fetch XML is available via the Web API or through Power Automate but cannot be used directly from a Canvas Power App.
FetchXML builder is a great tool for learning about and generating FetchXML queries.
I am currently using FetchXML within Power Automate for a model-driven app to run some very complex queries and process data across multiple tables. So to answer your question, I don’t think complex queries across multiple tables is a reason not use Dataverse.
#1
mmbr1606
22
Super User 2025 Season 1
#2
stampcoin
19
#3
Michael E. Gernaey
15
Super User 2025 Season 1
Share
Report
All responses (
Answers (
