Skip to main content

Preserve Layout Space for Hidden Fields (CRM)

A new company setting controls how hidden dependent fields affect form spacing. You can keep the empty space to preserve the layout or automatically close the gap for a more compact form.

Some fields on your forms appear or disappear automatically based on other answers (field dependencies). This new company setting lets you choose what happens to the space a hidden field leaves behind: keep it as blank space so the rest of the form doesn't move, or close the gap so the form looks more compact.

Contents

1. Before You Start

2. Open the Company Details Setting

3. Choose Yes or No

4. What Changes on Your Forms

5. Frequently Asked Questions

1. Before You Start

You will need:

  • An administrator account for your CRM instance

  • At least one field-dependency rule configured (Settings → Module Management), if you want to see the effect on a form

Access requirements: only administrators can change this setting. It applies to your entire instance — every user sees the same behavior.

If you don't see the setting on your Company Details page, your instance may not have the latest update yet — contact Dazos support.

2. Open the Company Details Setting

From the CRM, click the settings icon and navigate to Configuration → Company Details.

Scroll down the page — you will find the new row Preserve Layout Space for Hidden Fields among the company options. It shows the current choice (Yes or No).

Tip: If you have never changed this option, it reads Yes — that is the standard behavior your users already know. Nothing changes until you explicitly switch it.

3. Choose Yes or No

1. Click the Edit button at the top right of the Company Details page.

2. Scroll to Preserve Layout Space for Hidden Fields and pick an option from the dropdown:

Option

What it means

Yes

(default)

A hidden field keeps its spot as blank space. Surrounding fields stay exactly where they are, so the form layout never shifts.

No

A hidden field is removed from the layout completely. The fields below it move up and the form closes the gap.

3. Click Save.

The choice takes effect immediately for everyone on your instance — users just need to reload the page they are working on.

4. What Changes on Your Forms

The setting applies wherever field-dependency rules hide fields: record view pages, edit forms, and mass edit windows. Which fields hide or show is not affected — only the spacing. With Yes, a hidden field leaves blank space, keeping every other field in its usual place:

With No, the same form closes the gaps and looks compact:

Important: In side-by-side layouts, a row is as tall as its tallest field. If a hidden field sits next to a very large one (for example a big text editor), you may still see some empty space in that row even with No selected — the hidden field itself takes no space, but its tall neighbor still holds the row open.

5. Frequently Asked Questions

Q: We never touched this setting. Did anything change for us? No. Instances that have never saved the option behave exactly as before — blank space is preserved (the same as choosing Yes).

Q: Does this change which fields are hidden or shown? No. Your field-dependency rules keep working exactly as configured. The setting only controls what happens to the empty space.

Q: Who is affected when I change it? All users on your instance, on all modules, as soon as they load or reload a page. There is no per-user or per-module override.

Q: Can I switch back? Yes, at any time. Edit Company Details, flip the option, and save — no data is affected either way.

Q: Why do I still see a blank area after choosing No? Check whether the hidden field sits beside a tall field (like a large text box). The row stays as tall as its tallest visible field. The hidden field itself no longer takes any space.

Q: Does this apply to reports, lists, or printed PDFs? No. It only affects how record view, edit, and mass-edit forms are laid out on screen.

Need Help?

If you run into issues:

1. Reload the page (or sign out and back in) and check the Company Details page shows the option you expect.

2. Verify the field is hidden by a field-dependency rule — fields hidden for other reasons (permissions, layout configuration) are not affected by this setting.

3. Contact Dazos support and reference CRM-3469.

Did this answer your question?