Making one field Editable = False is fine. Making 50 of them? That’s the kind of task that makes you close VS Code, grab another coffee, and wonder why you didn’t say no to the request in the first place.
Learning how to add a similar property in all fields at once turns a repetitive slog into a quick, reliable process. With the right approach in VS Code, you can make bulk edits in minutes, keep your extensions clean, and cut down on mistakes.
In this guide, we’ll walk through exactly how to do it and share a few tips that make bulk changes in Business Central (BC) much less painful.
Key Takeaways
- Open the target AL object: Load the correct table or page .al file in VS Code and confirm you’re editing the right object.
- Select all fields: Use Ctrl + F2 (Windows) or Cmd + F2 (Mac) to highlight all the field definitions you want to update.
- Position cursors: Move each cursor to the end of the field line, hit Enter, and prep new lines for property insertion.
- Insert property: Add the property you want (e.g., Editable = false;, ApplicationArea = All;, or a tooltip).
- Save and publish: Save the file, then publish with AL: Publish without debugging to push updates to Business Central.
- Verify in client: Test fields in BC to make sure properties behave as expected (read-only, visible/hidden, default values, etc.).
Why Bulk Field Customization is Needed
Making the same property change across dozens of fields may feel repetitive, but there are plenty of situations in Microsoft Dynamics 365 Business Central where it becomes necessary. These include:
- Fields on posted documents that must stay locked once transactions are finalized
- Audit fields like Created By or Last Modified Date that should never be editable
- Compliance-related fields that need consistent restrictions across multiple tables or pages
These are not isolated cases. In most Business Central implementations, one minor customization request can lead to dozens of field updates across multiple objects.
Risks of Applying Properties Inconsistently
Applying a property to some fields and forgetting others creates problems later. A single editable field that should be locked can cause compliance issues, inaccurate reporting, or unnecessary data changes. Developers are also at risk of wasted effort during upgrades when inconsistent setups need to be corrected manually.
Consistency in these changes matters as much as the customization itself. Without it, projects can slip, quality drops, and users lose trust in the solution.
Step-by-Step Guide to Adding a Similar Property Across Fields
Using Visual Studio Code, you can update all fields of a table or page in one go, keeping your Business Central field customization consistent and error-free. Here’s a full walkthrough.
Step #1: Open the Target AL Object
Before adding a property, ensure you are working in the correct object:
- Open the .al file for the table or page you want to update in VS Code
- Scroll to the section containing all field definitions
- Verify the object is correct to prevent changes in the wrong location
Teams that partner with Aegis Softtech benefit from expert guidance in structuring tables and pages efficiently, ensuring bulk customizations stay precise and safe.
Step #2: Select All Fields for Editing
To apply a property across multiple fields, you need to select all the relevant field definitions:
- Place the cursor on the first field definition you want to modify
- Press Ctrl + F2 (Windows) or Cmd + F2 (Mac) to multi-select all instances of that field pattern
- Confirm all target fields are highlighted before proceeding
Step #3: Position the Cursor for Property Insertion
Next, position the cursors so that the property can be added correctly to each field:
- Select End to move each cursor to the end of its line
- Press Enter to create a new line under each field definition
- Verify that every selected field now has a cursor ready for property input
Step #4: Insert the Property
Now add the property you want to apply across all fields. Here are common examples:
- Use Editable = false; to make fields read-only
- Use ApplicationArea = All; to make fields visible to all roles
- Use ToolTip = ‘Enter value here’; to add guidance for users
Step #5: Save and Publish Changes
After inserting the property, save and deploy your changes to Business Central:
- Save the .al file in VS Code
- Press Ctrl + Shift + P and select AL: Publish without debugging
- Open the page or table in Business Central to confirm the property has been applied
Publishing immediately allows you to verify the results in the client environment.
Step #6: Verify the Property Works
Finally, test that the property behaves as expected:
- Confirm fields are read-only if Editable = false; was applied
- Check visibility or hidden fields for correct display
- Test default values and validation rules to ensure accurate data entry
Types of Field Properties in Business Central
It’s important to understand how individual properties affect user interaction and data control. Let’s walk through some of the key fields in Business Central.
Editable/ReadOnly Properties
The Editable property determines if a user can change a field value. When set to false, the field becomes read-only on a page, even though the table itself may still allow edits. Page-level settings override individual ones, which matters when applying restrictions across larger sections.
You might use it to:
- Lock audit fields such as Created Date or Modified Date
- Prevent edits on posted document fields to protect historical accuracy
- Disable input across a group of related fields for consistency
Visible/Hidden Properties
The Visible property decides whether a field shows up on the UI. Developers often pair it with Boolean variables or triggers to dynamically show or hide fields, keeping pages clean and intuitive.
Practical cases include:
- Hiding fields only relevant to certain workflows
- Revealing additional options during OnOpenPage or OnInit events
- Streamlining complex layouts by hiding advanced settings
Caption and Formatting Properties
Captions and formatting improve readability and multilingual support. For Business Central page properties, captions define how fields appear, while formatting ensures data, such as like decimals or currency, looks consistent. Developers rely on these settings to create a user interface that feels clear across different regions and languages.
Here are the most important ones to know:
- Caption provides the label that users see in the UI
- CaptionML handles translations for multiple languages
- AutoFormatType and DecimalPlaces control how numbers, currencies, and decimals display
Validation and Default Values
Validation and defaults play a big role in keeping records accurate.
Setting rules and initial states helps developers reduce the chances of bad data creeping into the system. These properties are especially important when applying how to add a similar property in all fields at once, since errors compound quickly across multiple objects.
Some commonly used settings include:
- InitValue to set a default when creating new records
- FieldValidate to enforce rules through validation logic at input
- ValidateTableRelation to ensure entries match records in related tables
Best Practices for Bulk Customization in Business Central
Bulk property changes can save time, but without care, they can create bigger headaches later.
Follow these best practices to ensure Business Central field customization remains maintainable, reliable, and ready for future updates.
Test Changes in Sandbox Environments
Always verify bulk updates in a sandbox before deploying to production. Testing allows you to catch issues early and ensures your changes work as expected. When preparing for testing, consider:
- Confirm that fields set to Editable = false; or Visible = false; behave correctly in the client interface
- Validate workflows, reports, and page navigation to ensure no unintended side effects
- Check for interactions with existing extensions, triggers, or automation processes
Sandbox testing prevents errors from affecting live data and gives teams confidence that changes are safe to deploy.
Avoid Over-Customizing Standard Objects
Excessive customization of standard tables or pages can create upgrade headaches. Keep modifications minimal and intentional. Here are some tips:
- Limit changes to fields critical for business processes
- Extend standard objects using AL extensions instead of direct modifications
- Focus on maintaining a clean separation between standard and customized functionality
Document All Property Changes
Keeping a detailed record of bulk property changes makes ongoing development and troubleshooting much easier. Effective documentation should:
- Specify which properties were applied to each field, such as Editable = false;
- Explain the business reason for the change and any dependencies on other fields or pages
- Include instructions for reversing changes if needed
Good documentation ensures transparency and keeps the team aligned.
Prepare for Upgrades (Extension vs. Modification)
Plan bulk updates with upgrades in mind to avoid conflicts with new versions of Business Central. Key considerations include:
- Apply bulk property changes via extensions wherever possible to preserve standard objects
- Avoid direct modifications to base tables or pages unless necessary
- Test your extensions against new releases before production deployment
Simplify Multi-Field Customization in BC With Aegis Softtech
Learning how to add a similar property in all fields at once ensures your BC tables and pages remain consistent and accurate.
The structured steps detailed in this blog post reduce errors, sandbox testing verifies changes before deployment, and thorough documentation protects standard objects while preparing your customizations for future upgrades.
Executed correctly, bulk property updates save time and maintain data integrity.
Aegis Softtech delivers precise Business Central field customization solutions. Our team applies bulk property updates, enforces best practices, and ensures pages, tables, and validations perform as intended. We also manage extensions, plan for upgrades, and verify functionality so your Business Central environment remains reliable and scalable.
Contact us today to maintain clean, consistent, and maintainable customizations.
FAQs
1. Can I bulk apply a property to fields in posted documents?
Yes, you can apply the same property to multiple fields in posted documents using Visual Studio Code. When you learn how to add a similar property in all fields at once, you can update table or page fields efficiently while maintaining data consistency.
2. What are the best practices for customizing fields in AL code?
Focus on structured and maintainable Business Central field customization. Group related fields, test updates in sandbox environments, document all changes, and prefer extensions over direct modifications. This approach keeps pages and tables consistent, reduces errors, and simplifies future upgrades.
3. Does bulk customization affect Business Central upgrades?
Yes, if changes modify standard objects directly. Applying bulk updates via extensions protects standard tables and pages, making upgrades smoother. Planning and documenting all updates ensures your Business Central page properties remain consistent and your environment stays compatible with future releases.
