Update devenv-lists-as-tiles.md #3371
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR is created to follow up on the question asked in #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."
|
Learn Build status updates of commit c104ac1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
jswymer
added
the
investigating
NKarolak
approved these changes
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is created to follow up on the question asked in #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 defined 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 AccessByPermission defined on table level then this field won't be visible to users without that permission."