Hi @Tal22
Power Apps are applications that have many years of experience and are mature enough for large organizations to use, even the Dynamics 365 modules are Power Apps with other business logic based on the nature of the process.
Another thing you should know is that Dataverse is a SQL with rich logic and metadata included and this is where you should start to understand how the model works.
There are certain components like Choices that cannot be removed because they are part of that meta, but the fact that they cannot be removed does not mean that you have to use them.
Dataverse and Model Driven Apps bring a series of components already built that you decide whether to use or not.
I'll give you an example, there is a table called account, you decide if you use it or not, if you don't want to use it you can create a new table.
In the case of Choises it is exactly the same, for example there is one called industry, you decide if you use it under the given scheme, or create a new one.
The issue having dependencies is not necessarily a problem because in the end you decide what is seen or not within an application, if you do not want that field to be seen you remove or hide it from the form or a view.
In the end it is understanding how a tool that has been working perfectly for years and that evolves to improve many processes works.
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
You can accept more than one post as a solution
