Small and medium business | Business Central, N...

Unable to remove certain actions through personalize or customize

(8) Share

Report

Posted on by Brett F

450

Hi,

We used to have these removed from certain users - New Line and Delete Line. At some point they were added back in by the system (I am assuming with an update) and we are no longer able to hide them. Is this just us or is this now standard?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Suggested answer

Sumit Singh 9,997 on at

Like (2)

Report
Yes, you're not alone. This issue has been reported by other Business Central users as well. These actions—"New Line" and "Delete Line"—were previously removable via personalization or role customization, but recent updates have changed that behavior.

Root Cause

Base Page Restrictions:

For standard (base) pages like the Sales Order Subform, Microsoft does not allow modification of InsertAllowed, ModifyAllowed, or DeleteAllowed properties via customization.

These properties control whether the Manage tab (which includes "New Line" and "Delete Line") is shown.

Update Behavior:

A recent platform update appears to have reset or overridden previous customizations, re-enabling these actions even if they were previously hidden[1].

This is likely due to Microsoft enforcing consistency across standard UI components to avoid breaking functionality or introducing unsupported states.

Customization Limitations:

Even if you use Visible = false in a pageextension, users can re-enable these actions via personalization, unless the field or action is completely removed from the page object.

For custom pages, you can still control visibility using InsertAllowed = false, etc., but not for base pages.

🛠️ What You Can Do
Option 1: Use Permissions to Restrict Functionality

While you may not be able to hide the buttons, you can prevent their functionality using permission sets:

Remove Insert or Delete permissions on the underlying table (e.g., Sales Line).

This will cause an error if the user tries to use the action, even if it's visible.

Option 2: Use AL Extensions for Custom Pages

If you're working with a custom subform or list part, you can:

pageextension 50120 MyCustomSubformExt extends "Sales Order Subform"

{

    InsertAllowed = false;

    ModifyAllowed = false;

    DeleteAllowed = false;

}

This will completely disable the ability to add or delete lines.

Option 3: Raise a Microsoft Support Ticket

If this behavior is breaking your business process, consider raising a support request with Microsoft to:

Confirm if this is a permanent design change.

Request a feature enhancement to allow hiding these actions again.

References
[1] Solved: Hide manage action from list part - Dynamics 365 Community
[2] Customizing Pages for Roles - Business Central | Microsoft Learn
Note: This response was created in collaboration with Microsoft Copilot to ensure clarity and completeness. I hope it helps to some extent.
Mark the Answer as Verified if this is Helpful.

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,136 Super User 2025 Season 2 on at

Like (3)

Report

Adding more details

https://community.dynamics.com/forums/thread/details/?threadid=cc0840e9-dc26-4263-b2d2-df3159b7aa98

https://stackoverflow.com/questions/77855260/change-or-hide-a-custom-action-from-the-standard-page-in-ms-d365-business-centra

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,329 Super User 2025 Season 2 on at

Like (2)

Report

Not sure how you've hidden it before.
To hide this standard behavior, there are generally two ways:

1. Set the page's DeleteAllowed Property and InsertAllowed Property to false

More details: Business Central 2024 wave 2 (BC25): Support for modifying the properties InsertAllowed, ModifyAllowed, and DeleteAllowed of a page

https://yzhums.com/56456/

2. Use permission management to prohibit insert and delete this table data.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Mansi Soni 8,907 Super User 2025 Season 2 on at

Like (5)

Report

Hello,

https://community.dynamics.com/forums/thread/details/?threadid=39c0e199-7ce7-4983-a890-b3f538063f1b

Hope this will give you some hint!

Regards,
Mansi Soni

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,154 Most Valuable Professional on at

Like (3)

Report

Hi

You could try using profile customization from the Profiles (Roles) page, which allows for deeper adjustments than user customization.

Customizing Pages for Roles - Business Central | Microsoft Learn

Best

GR

Was this reply helpful? Yes No
Suggested answer

Kamal Khakhkhar 1,274 on at

Like (2)

Report

Hii There , as per that actions are not available in Page . for that insert allow, delete allow property of page used. so if you can update that you can control the actions of you mentioned.

If You found answer , mark it answered.

Thank You.

Kamal Khakhkar

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 8,760 on at

Like (2)

Report
Hi Brett,

It seems that the “New Line” and “Delete Line” actions are core system actions, typically embedded in subpage structures or repeaters. If they previously disappeared and have now resurfaced, it’s most likely tied to an update or base object change in the environment.

Here’s how BC handles this and how you can regain control:

Why These Actions Return Unexpectedly

Personalization hides actions at the user level only — and it’s sensitive to updates, role switches, or schema changes.

If Microsoft modifies or rebuilds the page object during a minor or major release, personalization layers may reset and restore hidden system actions.

Actions tied to system commands (like Insert or Delete) on subpages often ignore personalization visibility when the base object changes.

Recommended Approaches to Restrict These Actions

Option 1: Role-Based Customization via Profiles

Go to Profiles (Roles) → select the target profile → choose Customize Pages.

Hide the actions via the profile rather than individual users. This ensures:

Greater persistence across updates

Global control for users under that role

Option 2: Page Extension for Action Suppression

Use AL to modify the action’s visibility at the page level:

This permanently suppresses these actions across all sessions and survives upgrades.
al modify("New Line") { Visible = false; } modify("Delete Line") { Visible = false; }

Option 3: Restrict via Permissions

If suppressing visibility isn’t possible (e.g., for deeply embedded system actions), remove insert/delete permissions via Permission Sets.

This causes action attempts to trigger an error — not ideal for UX, but enforceable.

Option 4: Disable Personalization Globally

In the Profiles page, toggle Disable Personalization = TRUE for users where visibility must remain fixed.

This locks down UI customization and prevents action toggling from the frontend.

Helpful References:
Understanding Action Visibility Layers – GitHub Thread
Role-Based UI Customization – Dynamics Tips
Permission Set Design for UI Control – Microsoft Learn
Customize Pages per Role – Microsoft Learn
Page Object Extension – Microsoft Learn

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No