Unanswered

What is the EASIEST method to combine data from a chain of related tables AND display that data in the dropdown in Dataverse table

(0) Share

Report

Posted on by MJWhite

338

I have three tables: Frameworks (have many) Categories (have many) Subcategories. In the Subcategories table, I want to view the concatenation 'Framework, Category' in the dropdown for Category (see screenshot below).

I have previously posted this problem as two separate questions, but I realize I want to be able to do both:

The answer to Is there an equivalent of SQL Views in PowerPages to view data across multiple tables? was: Using Dataverse views you can only see the primary table + parent tables data. If you need something more advanced, you will need to build your query using WebAPI or Fetch and to a custom render of the results
The answer to Is it possible to change the field displayed in a dropdown in a data table? was: Use a Workflow, Plugin, Flow (flow only if it does not need to show up immediately - as it has no real-time option), if it only needs to occur via the user interface you can use JavaScript

Since I want the data to be displayed real-time in the Dataverse table, the above answers suggest four possible ways of doing this:

WebAPI
Fetch
Workflow
Plugin

Since this is such a common requirement in any application, I'm hoping someone might might be able to suggest the easiest method.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

natalya 133 on at

Like (0)

Report

Hi @MJWhite,
It's possible to show the different value in the dropdown field by using JS.
Other solution would be to create the field in the table with all possible combinations to show in the dropdown.

Hoping it helps.
NatGeo

Was this reply helpful? Yes No
MJWhite 338 on at

Like (0)

Report
Thanks. As I understand it:
The dropdown will only display the data in the primary field in the parent table
The primary field in a parent table cannot be a calculated field
I have reluctantly accepted that the simple, low code solution to this problem is to populate the primary field in the parent table with the required text. I say reluctantly, because this creates a data maintenance issue, as the same data will now be stored in two places.
It surprises me that Dataverse doesn't offer a better solution to what is a common, basic requirement for all databases.

Was this reply helpful? Yes No