I'm starting with with CDS and model-driven apps and decided to try on recreating a simple scenario.
I have an Excel report that is build by calculating fields from multiple sheets using vlookups, so I thought I would re-create each sheet as new entity in CDS and then have a "master" entity with calculated fields that would show data from others base on formula similar to vlookup. And that's where I'm failing...
Could somebody please help me jump start my brain and point me in the right direction or to a good source?
Any assistance is highly appreciated
Hi @Ifrit ,
In CDS we use relationships to join entities (entity = Excel table) instead of using vlookups. Basically, entities can have a reference (lookup) to other entities that it is related to. This could be quite a learning curve if you are not familiar with databases and relationships but here is some documentation to get you started.
Have a read through all the pages in the Work with entity relationships section and then come back if you have any further questions.
Thank you for the quick response.
I have read all the articles and understand it on base level but I think I'm still not able to replicate my scenario.
What I think would help me is specific example to unstuck my brain.
let see I have 2 entities, Entity A has ID field and Entity B has ID and Country field.
How would you create calculated text field that would show country if ID of A and B match?
Thank you for all the help
I managed what you described working before but it isn't exactly.
I understand the concept but what if I don't care about form input. I populate entity with records from another datasource and the same for IDs of Entity A. How do I auto-populate the lookup with the right value since I can't calculate it?
Did you ever get a workable solution to this question? I am trying to do the same thing but haven't been able to find a good solution?
So in your scenario you have a country on one entity and if you have that Record id on another record via a relationship, you want to display the value of the country from record a on record b
possible solutions include using a quick view form to display parent record fields on child—that’s how we show account fields on child contacts
also calculated fields can use values from the related record
and views can display fields from related records
If the records are not directly related, use power automate to copy the value of you aren’t concerned about the data being in different entities
Power Apps User Groups are coming! Make sure you’re among the first to know when user groups go live for public preview.
Did you miss the call?? Check out the Power Apps Community Call here!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.