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

What is the best method to configure the BC if you have customized page

(7) Share

Report

Posted on by Manikandan Subramani

Hi Team,

I have a scenario and I need a best option for that.

I have a BC environment it has 2 companies under that. I have a customized page in the Sales order page. I need that same customized page to be shown in one company with 10 fields and another company with 5 fields. Simply, I need a suggestion that how to handle different customization on the same page under same environment. What is the best practise in Business Central.

Thanks,

Mani

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Khushbu Rajvi. 21,573 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Please check this: I have explained the same scenario in the below blog

Business Central Junction 365 Blogs: Dynamic Visibility of Controls Company Specific (Hide and show fields dynamically)

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,876 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
Hi,

You can control field visibility on a page by using Boolean global variables.

You can create one Boolean variable per field if each field’s visibility is different.

If multiple fields should behave the same way, you don’t need separate variables for each field.

Example:

If you have 10 fields and only 5 of them need to be shown or hidden together:

Create one Boolean variable, for example ControlVisible

For those 5 fields, set the property: Visible = ControlVisible;

Now, you only need to change the value of ControlVisible to show or hide all 5 fields at once.

You can set the value of this Boolean variable in the OnOpenPage trigger.

The value of the variable can be decided:

Based on Company Name (hard-coded), or

Based on a setup field, for example:

A Boolean or Option field in Company Information Or General Ledger Setup

Based on the setup value, you set ControlVisible to TRUE or FALSE.

This way, the same page can behave differently for different companies within the same environment.

Regards,

Dhiren.

Was this reply helpful? Yes No
Manikandan Subramani 54 on at

Like (1)

Report
Copy link

Link copied!

Thanks for your response Dhiren and Khushbu.

Assume if the changes between the companies not only field visibility. Additionally, if it has more logic difference and the structure difference what should we do? Do we still need to do the customization based on the company or do you prefer separate environment and separate customization?

Thanks,

Mani

Was this reply helpful? Yes No
Suggested answer

Ben Baxter 6,833 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

The easiest, no code solution is to use a Profile per company. For Example, Sales Agent - Comp 1 and Sales Agent - Comp 2. Each Profile controls what is visible on the specific pages and are easy to update should a field become needed in either company.

This is assuming the Users are interacting with one company, as the profile doesn't change when you change companies. So as long as the Users remain in their designated company, the profile allows you to accomplish your goal with zero development.

Best Regards,

Ben Baxter

Accent Software Inc

Was this reply helpful? Yes No
Suggested answer

Andrés Arias 4,790 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

The simplest recommendation would be to make a small customization to meet the requirements of the scenario.

You could also determine different roles and customizations, but maintenance would have to be done per user, which is complex.

I hope this helps.

Regards,

Andrés

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 11,606 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello Mani,

Best practice in BC is one page extension, behavior controlled by company-level setup, not multiple page customizations. Add all 10 fields in the page extension, then show/hide fields dynamically using either Company Information, a custom setup table, or Feature Management flags, and control Visible = MySetup.ShowFieldX in AL. This keeps one app, one page, upgrade-safe, and avoids branching logic or multiple extensions per company. Avoid hardcoding CompanyName() checks unless it’s a quick workaround; a setup-driven approach is the recommended and supportable pattern in Business Central.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No