Can we have a feature to hide standard entities in CDM?

[JulianKirkness]

I find the number of entities in CDM really unhelpfull when tryin to build something. Could we have an option to hide any we don't want to use please?

[I also have a view about the HR related entities - I am a specialist in HR software and have been for about 25 years - I don't thinl I would use these entities because they aren't set up the way I would want (they're too basic). I feel this is a flaw in the concept of the standard entities generally and will make it difficult, as an ISV, to use it.]

[pturner]

Agreed.

At least let us hide them if we can't delete them.

[Vijeta]

Thank you for your feedback. We are working on adding functionality to give you the ability to filter the list of entities displayed based on category, type of entitiy (Standard vs. custom) etc.

We have not added HR category of standard entities yet.

[JulianKirkness]

Hi Vijeta

Glad to hear about the new features you're working on...

In terms of HR, I have only really looked at the employee entity which, for example, has a Department field. Generally in an HR system you would design the system with an Employee table, a Jobs table and a Departments table - someone's department would be determined by their job via the relationships.

In the public sector in particular it can get more complex with people often having more than one Job at once (and hence department etc).

What I suppose I'm getting at, is that the CDM is likely NOT going to fit many specific scenarios well and may well lead to compromises in design which will be cumbersome - just so the app fits the standard model. As an ISV (I currently sell Access Web App based apps on the Sharepoint Store) I'm not sure how it will work being constrained by someone else's database design. Having said that, I applaud the fact that you are building a Power User database for PowerApps and I guess it may save some time.

[Audrie-MSFT]

We are working on adding functionality to give you the ability to filter the list of entities displayed based on category, type of entitiy (Standard vs. custom) etc.

Thank you for your continued feedback and ideas,

Audrie

[jmc]

Idk why we can't just delete them in the first place...

[shakudu]

Having an enviroment with hundreds of premade entities that we don't plan to use... ever, is frustrating. It makes it harder to locate our custom entities and makes the whole development process a bad experience.

Coming from actual programming to trying to develop something in powerapps is hard enough without someone deciding what my needs should be.