Forum Discussion
Dataverse lookup columns
I have a question about using lookup fields in Dataverse. I have been developing in Access using Dataverse as the data tables. In Access, using Lookup fields is not a good practice. Does the same app...
Lookup fields in Dataverse appear to introduce some of the same complicating factors that we battle in Access tables. In reading the "gotchas" listed, an old saying comes to mind from my childhood days. It refers to the days when general stores sold commodities like sugar, flour and beans from open barrels. Customers could serve themselves by putting some of the commodity in a "penny sack". The saying goes, "that's too much sugar for a cent." Meaning the appearance of Lookup columns in tables promises sweets, but they cost more than the supposed price.
Use them at your discretion.
Use them at your discretion.
I got two differing opinions here, so I am not sure which way to go. Should I create relations using the Relationship Tool in Dataverse table?
- It's really up to you, in the final analysis. IMO, the interface for Dataverse tables is overly complicated because it tries to wrap the underlying realities of tables in structures like the Lookup tables and so on. After some initial attempts to incorporate Dataverse tables, I went back to the tried and true, i.e. SQL Azure or SQL Server.
Performance is not as impressive either. But ultimately, if Dataverse provides you something unavailable elsewhere, then it's okay.
Don't let others, who are either enthusiasts or skeptics, override your own experience.