Skip to content

Commit d7a4fb5

Browse files
authored
Merge pull request #3064 from mspilde/patch-8
Update form-designer-header-properties.md
2 parents b235544 + 24a2bfa commit d7a4fb5

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

powerapps-docs/maker/model-driven-apps/form-designer-header-properties.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Configure header properties in the form designer | MicrosoftDocs"
33
ms.custom: ""
4-
ms.date: 09/30/2019
4+
ms.date: 06/26/2020
55
ms.reviewer: ""
66
ms.service: crm-online
77
ms.suite: ""
@@ -87,7 +87,8 @@ To show or hide the header flyout for a model-driven form, follow these steps:
8787
> - Use the new form designer. The classic form designer does not provide the ability to show or hide the header flyout.
8888
> - The visibility of header flyout can only be controlled when using high-density form header. When using low-density header, the header flyout is automatically displayed or hidden based on the number of fields in the header and the width of the form.
8989
> - An image for an entity will be displayed in the header only if the **Primary Imagine** attribute is defined for the entity and the form property **Show image in the form** is enabled. More information: [Image fields](../common-data-service/types-of-fields.md#image-fields). <br />
90-
Developers can specify an image for an entity by using the [EntityMetadata.PrimaryImageAttribute](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.metadata.entitymetadata.primaryimageattribute?view=dynamics-general-ce-9) attribute.
90+
Developers can specify an image for an entity by using the [EntityMetadata.PrimaryImageAttribute](https://docs.microsoft.com/dotnet/api/microsoft.xrm.sdk.metadata.entitymetadata.primaryimageattribute?view=dynamics-general-ce-9) attribute.
91+
> - When using a high-density header on a form, controls are limited in what is displayed that include a checkbox, datetime, decimal, duration, emailaddress, float, integer, languagepicker, lookup, money, phonenumber, picklist, radio, regarding, textbox, ticker and timezonepicklist. Any other type of control, including custom Power Apps control framework controls, will not be displayed. You'll need to switch to the high-density header with flyout to ensure your users can access controls in the header that aren't in the supported list.
9192
9293

9394
## Form designer messages related to form headers

0 commit comments

Comments
 (0)