Hi Sik,
Thanks for the response. I'm aware of the advantages of using relational databases for entities just as you mentioned, and thank you for giving some additional thoughts in terms of requirements.
In terms of actual development in Power Apps, does this have an impact on how we configure/code these data over manually creating two entities and relating them via a unique reference ID?
We're using CDS now. Previously in SharePoint, we basically just do that - creating two lists (List A and List B).
List A - The main form (let's say a budget request)
List B - the line items of the budget request
In SharePoint, we relate the two lists by using the GUID/ID of SharePoint (List A Item 1 has ID = 1), so when we submit the record in Power Apps, we have a function to call the LastSubmitted ID and write that in a column for List B (so that List B Item 1 has ColumnID = 1 as well).
Now that we're on CDS, there's this feature of creating relationships between entities (I assume these are lists when you compare them in SharePoint). Will the logic be the same as above when I code/configure them in Power Apps?