Missing functionalities in new Solution Explorer / new Customization Experience pt. 1

Finally I started using the new customization experience on a regular base and in general I have to admit that I really like it. However there are still some shortcomings compared to our good old Solution Explorer.

More (white) space

One thing is that it takes more space in many aspects, because, at least this is what I think, Microsoft wants to be ready for touch screen users using and customizing) their system.

As this is related not only to the customization experience but also in general to the front end of all Model Driven Apps, I would really wish to have a button or setting somewhere the Personal Settings where I as a User can switch between mouse usage and touch usage. But at the moment I don’t think that this is somewhere in focus for MS.

On the other hand my assumption is that having a more streamlined customization portal that is more aligned to the front end saves valuable developer resources for MS because UI adjustments always take some additional time.

Missing Table Name (Primary Entity) in Processes View

In the old experience you could easily see which table/entity a Process is based on:

In our new experience this column is not there anymore which makes it unnecessarily hard to get an overview of which processes are used on which table.

Therefore I’m still preferring the old entry gate for customizing processes.

Missing Description column

In the old component overview we had a column “Description”. I often use this to leave a kind of technical hint like “Used on Contact-Form”.

In new component lists I’m really missing that column:

Missing Publish-button on “entity” level

In old experience we had this useful Publish button on entity level. You could press it to publish only components from the same entity/table at once. This happens often that after having edited something you just want to publish this table/entity only.

In the new experience I can’t really find something similar an entity level. Only after editing a View or a Form or similar you can publish this single component.
Publishing the whole solution however takes much longer than what it took to publish the Entity only.

Share it on

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.