web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

How to hide a standard field and prevent users from adding the field again

(0) ShareShare
ReportReport
Posted on by 25

I hided a standard field on a standard page using "Visible = false" in a page extension.

How can I make it impossible for users to add the field again in the page personalization?

I have the same question (0)
  • JAngle Profile Picture
    133 on at

    Try: docs.microsoft.com/.../devenv-enabled-property

  • Thorsten Kern Profile Picture
    25 on at

    I tried "Enabled = false", but the field is still displayed as a column on the list page.

  • Suggested answer
    JAngle Profile Picture
    133 on at

    What about: docs.microsoft.com/.../devenv-accessbypermission-property

  • Thorsten Kern Profile Picture
    25 on at

    The requirement is that the field should no longer be visible to any user. I was hoping that a standard field could be completely removed from a standard page (e.g. item list). The AccessByPermission property sounded to me like a user with the SUPER permission set would see the field anyway. Is that correct?

    Still, it could be a workaround. I will give it a try.

  • Suggested answer
    JAngle Profile Picture
    133 on at

    Last option from me: docs.microsoft.com/.../devenv-applicationarea-property

  • Thorsten Kern Profile Picture
    25 on at

    Thank you. I will share the result.

  • Thorsten Kern Profile Picture
    25 on at

    Message: "The property 'AccessByPermission' cannot be customized.AL(AL0246)"

  • Thorsten Kern Profile Picture
    25 on at

    "Application areas enable hiding entire business scenarios and you can have the same code base, which makes it possible to quickly modify the UI for different business scenarios or audiences. However, tagging errors as missing tags or incorrect tags will occur and every single control will need to be tagged."

    (docs.microsoft.com/.../devenv-extending-application-areas)

    In this individual case, the effort seems a bit high. Are the application areas worth using in the long run?

  • Suggested answer
    Greg Enns Profile Picture
    1,106 on at

    Maybe try setting "HideValue = true"? This in addition to "Visible = false" seems like it would be sufficient.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,143

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,694 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,067 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans