Unanswered

Dataverse View how to add column for related table/entity?

(0) Share

Report

Posted on by DarkLiteOne

234

Because the standard table `Address` does not provide a way to lookup the 'Country' and the 'PostalCode' we created the following 3 tables:

Address
- Columns: StreetName, HouseNr, PostalCode
- Relationship: Address_ManyToOne_PostalCode
PostalCode
- Columns: PostalCode, CityName, Country
- Relationship: PostalCode_ManyToOne_Country
Country
- Columns: CountryName, CountryShortCode
- Relationship: Country_OneToMany_PostalCode

This all seems to be working fine. Now we would like to display the following columns in the 'Main' view called "Active addresses':

The issue is that we would like to display the 'CountryName' or 'CountryShortCode' in the View but these fields aren't available from the dropdown list when adding a new column. How is it possible to do this?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (10)

Answers (1)

joe_hannes_col 1,843 Super User 2024 Season 1 on at

Like (0)

Report

Hello again @DarkLiteOne,

You can add fields from related tables to a view in Dataverse. To do this, you will have to select the "Related" tab over the list of controls:
Then you can select one of the fields of the related table, in my case e.g. the Customer Project Reference.

Was this reply helpful? Yes No
Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (3)

Report

Hi @DarkLiteOne ,

You will only be able to add relationships using the Related as mentioned by @joe_hannes_col for relationships that are direct to the Address entity. You will not be able to go two levels deep (i.e being able to pull Country from the Postal Code that is related to the Address). You would need to add the Country lookup to the Address entity to be able to show fields from the Country table.

One thing on this that might be useful on a customer that I work with, they are using SmartyStreets to autocomplete address information and do address validation. Pretty low cost solution and a lot of functionality that can hopefully save you time and costs for building and maintaining these custom tables.

Hope this makes sense? Please accept if answers your question or Like if helps in some way.

Thanks,

Drew

Was this reply helpful? Yes No
DarkLiteOne 234 on at

Like (0)

Report

Thank you for your answer, that is indeed the problem, using a field that is linked 2 levels deep. We're not so keen on using an external API as SmartyStreet. I just thought there was a way to retrieve this data as the relationship is known to Dataverse. In SQL Server that would be resolved with a simple join.

Was this reply helpful? Yes No
peterharket 28 on at

Like (0)

Report

Any news on this?

Was this reply helpful? Yes No
Emile_1944 34 on at

Like (0)

Report

I am having the same problem here, but in my case, a lookup table wouldn't work because Dataverse doesn't allow the saving of multiple Sections Combo Box to a lookup column.

Please my original entry below. Thanks.
https://powerusers.microsoft.com/t5/Building-Power-Apps/Save-multiple-Section-Combo-Box-to-lookup-column-in-Dataverse/m-p/1581468#M405843

Was this reply helpful? Yes No
Emile_1944 34 on at

Like (0)

Report

More Dataverse limitations. 😞

Was this reply helpful? Yes No
CU07031518-0 18 on at

Like (0)

Report

Really a big limit !😑

Was this reply helpful? Yes No
CU07031518-0 18 on at

Like (0)

Report

I solved it by adding formula fields in the child table that retrieve data from previous levels parent tables

Was this reply helpful? Yes No
lmd-be 8 on at

Like (0)

Report

What am I doing wrong here compared to you?

I also tried User.FullName.

Is this a bug @dpoggemann ?
The User column is linked with the User table (systemuser).

I simply can't make it read the column. I have access to it from a view, but not in the table.

image_2024-02-22_...

Was this reply helpful? Yes No
Remondki Microsoft Employee on at

Like (0)

Report

This worked for me adding a formula column in the child table - parent table name.fieldname

Was this reply helpful? Yes No