{"id":14462,"date":"2021-04-27T11:59:27","date_gmt":"2021-04-27T18:59:27","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/improve-data-density-with-high-density-headers-in-model-driven-apps\/"},"modified":"2025-06-11T07:54:35","modified_gmt":"2025-06-11T14:54:35","slug":"improve-data-density-with-high-density-headers-in-model-driven-apps","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/improve-data-density-with-high-density-headers-in-model-driven-apps\/","title":{"rendered":"Improve data density with High-Density Headers in model-driven apps."},"content":{"rendered":"

Hello everyone,<\/p>\n

I wanted to share with you some thoughts on how to improve the overall productivity of your forms by moving from the \u201clow-density\u201d header to a high-density header in a model-driven app.\u00a0 If this is something you\u2019ve already done, then you know how the high-density headers can really help users understand the data they are working with on a model-driven form. This is important because the fields in the header represent the most important information a user needs to see to help them understand what information is on a form and what data a user will be working with.<\/p>\n

For forms over data (main forms) in model driven app we include some basic information that identifies the table and the record the user is working on in the form header.\u00a0 We also include information on the data if it is in a read-only state and we include notifications that you, as a maker, can define and errors that occur while working with data including data types (added a text where it should be numeric) or required fields.<\/p>\n

In this example the form has a\u00a0 high-density header<\/strong> with the four fields that are essential for a user to quickly scan and does not need to edit or need additional fields beyond what is included on the header.\u00a0\u00a0 To achieve this, you can set the form header in the designer to high-density and remove the option to show the flyout.\u00a0 This helps the user stay on task without distractions or unnecessary clicks in the header.<\/p>\n

Form Runtime:<\/strong>\"\"
\nForm Designer Settings:<\/strong>\"\"<\/p>\n

If you need to have more than four fields or need to have users edit the fields in your form header you will need to make sure you use the high-density with flyout<\/strong> option.\u00a0\u00a0 This can be easily set in the modern form designer.\u00a0 When this flag is set a small chevron will show in the right, like how low-density header worked but, in this mode, all the fields in the header will be available for a user to interact with including the four read-only fields that are rendered on the form.<\/p>\n

Form Runtime:<\/strong>\"\"
\nForm Designer Settings:<\/strong>\"\"<\/p>\n

In the example below you can see how data reflows in a high-density header and how information always wraps and is never truncated. This is vital for user to be able to always see important information especially when dealing with long table or record titles on a form.\"\"
\nIMPORTANT CHANGES<\/strong> \u2013 Removing low-density headers.<\/p>\n

It is also very important to know that low-density headers will be deprecated<\/a> in October 2021 with Release Wave 2.\u00a0 What that means is if you have not moved to a high-density header, with or without flyout, the platform will automatically change this at runtime.\u00a0 To ensure data entry is still available the runtime will set all low-density headers to high-density with flyout.<\/p>\n

We are making this change because:<\/p>\n