Hi,
From a fresh install of D365/PP Dataverse perspective, there is only 1 "copy" of the Account Table (aka entity before).
You would have to use it for both apps, and if you needed the apps to only see data that belong to "that app", you would have to create roles and
attribution on the Table to do that.
Super silly example would be to add an actual column that was defined as "Which App is this for" and then you would have some form of lookup or string or number that you define which App it belongs too, and in the App, you would code it to only pull back those rows.
Or again you would have a role, and you would have roles for App1 and App2, and the Rows of data would have some attribution that allowed only App1 or App2 to see it, and then of course, you would need roles to define the users App abilities etc.
Or you would have to create another "copy" of the Table and each App would point to that copy. Since technically the Label (visual string you see) for
tables can be the same even if you have 30 copies, it's the name (not the string label) that would be different. So you could name 30 tables Account, as long as the name you gave me, was something else. But this makes it super hard to tell which one to use, because in the UI of Dataverse, you just see 30 things labelled as Account. However people will still make copies and label it the same thing for their developers.
54
Share
Report
All responses (
Answers (
