Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update devenv-lists-as-tiles.md #3371

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

Update devenv-lists-as-tiles.md #3371

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion dev-itpro/developer/devenv-lists-as-tiles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down