Dazos

The Layout Editor is completely non-functional across your entire CRM instance:

Field visibility changes (hiding or unhiding fields) fail to save

After clicking "Save," fields revert to their original state

No changes are reflected on actual record pages

Affects all CRM modules (Leads, Accounts, Intake Opportunities, Referral Sources, etc.)

Cannot unhide mandatory fields required for lead conversion or data tracking

- Field visibility changes (hiding or unhiding fields) fail to save
- After clicking "Save," fields revert to their original state
- No changes are reflected on actual record pages
- Affects all CRM modules (Leads, Accounts, Intake Opportunities, Referral Sources, etc.)
- Cannot unhide mandatory fields required for lead conversion or data tracking

⚠️ Note: This is different from individual field hiding issues — this affects the entire Layout Editor system's ability to save any changes.

This indicates a system-wide bug affecting the Layout Editor's database communication. The interface appears to function normally, but changes are not being committed to the database, causing all modifications to be lost upon page refresh or navigation.

⚠️ Critical: Do not continue attempting to save changes — this is a complete system failure that requires professional technical intervention.

Stop making changes to field visibility immediately. Further attempts will not resolve the issue and may cause additional complications.

Contact Dazos Support immediately. This requires a Jira ticket for developer intervention.

- Your CRM instance URL
- All affected modules (typically all modules in the instance)
- Specific fields you were trying to hide or unhide
- Screenshots or screen recordings demonstrating the issue
- When the issue first started occurring

Await developer resolution. The development team will investigate the database communication issue and implement a fix.

Once notified the issue is resolved, test the Layout Editor across multiple modules to confirm the fix is working correctly.

1. Stop making changes to field visibility immediately. Further attempts will not resolve the issue and may cause additional complications.
2. Contact Dazos Support immediately. This requires a Jira ticket for developer intervention.
3. When contacting support, provide:
 - Your CRM instance URL
 - All affected modules (typically all modules in the instance)
 - Specific fields you were trying to hide or unhide
 - Screenshots or screen recordings demonstrating the issue
 - When the issue first started occurring
4. Await developer resolution. The development team will investigate the database communication issue and implement a fix.
5. Once notified the issue is resolved, test the Layout Editor across multiple modules to confirm the fix is working correctly.

After the development team resolves the issue:

Layout Editor changes will save and persist properly

Field visibility modifications will be reflected on actual record pages

All CRM modules will respond correctly to layout customizations

Mandatory fields can be properly unhidden for lead conversion and data tracking

- Layout Editor changes will save and persist properly
- Field visibility modifications will be reflected on actual record pages
- All CRM modules will respond correctly to layout customizations
- Mandatory fields can be properly unhidden for lead conversion and data tracking

Contact Dazos Support immediately if you experience this issue. This is a high-priority system bug that requires:

Jira ticket creation for the development team resolution

System-level fixes that only developers can implement

- Jira ticket creation for the development team resolution
- Backend database investigation
- System-level fixes that only developers can implement

Troubleshooting Standard Fields That Do Not Hide in Dazos (CRM)

How to Hide and Reactivate Both Active and Inactive Fields

Module Layout and Field Configuration guides

- Troubleshooting Standard Fields That Do Not Hide in Dazos (CRM)
- How to Hide and Reactivate Both Active and Inactive Fields
- Module Layout and Field Configuration guides

Overview
This guide helps resolve system-wide Layout Editor failures where field visibility changes are not saving across any CRM modules. This is a critical issue that prevents field customization and mandatory field configuration.

Troubleshooting Layout Editor Field Visibility Changes Not Saving System-Wide (CRM)

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

Try using different keywords or checking for typos.

No conversations found

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

Troubleshooting Layout Editor Field Visibility Changes Not Saving System-Wide (CRM)

Symptom / Error

Cause

Solution

Verification / Expected Result

Escalation

Related Resources