From c104ac1cfc3272347a8317e37751424c0644f82f Mon Sep 17 00:00:00 2001 From: jswymer Date: Thu, 19 Sep 2024 17:49:59 +0200 Subject: [PATCH] Update devenv-lists-as-tiles.md This PR is created to follow up on the question asked in https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb/pull/3367 regarding the note: "If I understand this note correct then the sentence maybe should be split into both scenarios. Field definied only on Table Object -> Field won't be shown on the tile Field is definied on the Page Object -> Field isn't visible to the user -> Field won't be shown in the tile view. To summarize: Field must be added to the Page Object and visible for the user. The last sentence in the current note mentions that the field should be added via personalization and then it's visible in the tile. If the field has an AccessByPerrmission defined on table level then this field won't be visible to users without that permission." --- dev-itpro/developer/devenv-lists-as-tiles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-itpro/developer/devenv-lists-as-tiles.md b/dev-itpro/developer/devenv-lists-as-tiles.md index 85a5fde979..ee045c0cff 100644 --- a/dev-itpro/developer/devenv-lists-as-tiles.md +++ b/dev-itpro/developer/devenv-lists-as-tiles.md @@ -53,7 +53,7 @@ The order of the fields determines how they appear in the layout of the tile, no - A verbose field appears at the bottom of the tile, separated by a line. > [!NOTE] -> The Tile view respects user permissions and visibility settings on fields, like the `Visible` property, personalization, and so on. For example, suppose you have a field defined in `fieldgroup(Brick; <...>)` but the field is only defined in the table object, not in the page object: This field doesn't display in the Tile view by default. Users can display the field by using personalization. +> The Tile view respects user permissions and visibility settings on fields, like the `Visible` property, `AccessByPermission` property, and personalization, and so on. For example, suppose you have a field defined in `fieldgroup(Brick; <...>)` but the field is only defined in the table object, not in the page object. This field doesn't display in the Tile view by default. Users can display the field by using personalization. ### Including images in tiles