This issue usually occurs when the field is already mapped to another field that was removed from the layout. Verify that the field lengths match and check the corresponding unused field based on its field type. If you cannot identify the field, share the Layout ID, field name, and a screenshot of the error for further investigation.
Check the storage limit by going to CRM Setup > Data Administration > Storage > File storage. If you are running out of storage, you can choose to purchase additional storage or delete unwanted files from the CRM to be able to proceed.
The "File not supported" error appears based on format-related issue. In such cases, check the file format of the upload and test by uploading in different formats like (.PNG, .JPG, .JPEG). If the issue persists, write to support with these details like the record ID, file format, screenshots or recording for us to debug further.
The limit for multi-select lookup fields is two per module. This means if two multi-select lookup fields have already been connecting to a module, that specific module will no longer be available for selection when attempting to create a new multi-select lookup field in another module.
Try again after refreshing your web browser or try on an incognito window. If the issue persists, contact support with reference screenshots or a recording to debug further.
First, try it in different browsers and also check for any validation rules or client scripts associated. If yes and possible, try disabling them and check. If the issue persists, please contact support by connecting on a live session to help us debug and assist further.
Apart from the basic section of each module, like Lead or Contact Details or any check box fields, check whether the field permission is available for all profiles of the fields. Only these fields will be listed under Show or Mandate options in the layout rules. It includes the fields used in the criteria or the sub-criteria as well.
Other than these conditions, if you have any concerns, contact support with these details like the layout rule ID, the field/section name that is not listed for selection, long with a screenshot or recording for further assistance.
Check whether the user has the field permission for all of the fields used in the layout rules. That includes the fields used in the criteria as well as the sub-criteria.
Check if you have sufficient field permissions to edit the fields mentioned in the criteria. If the issue persists, then share the record ID, the layout rule ID, and a screen recording showing the issue for further assistance.
The layout rule is expected to or trigger. if it doesn't, then write to us along with a detailed screen recording to check and assist further.
The "Reason for loss" field in the Deals module is a picklist field, and the visibility depends upon the Stage field. The reason for loss will only be shown when the default stage value like "Closed Lost" is selected. If any custom Lost stage values are chosen, it would not work.
As this could not be a common issue, it will need technical assistance. Please contact support for further assistance.
Currently, the Currency field won't be shown even though it should be a mandatory field.
Refresh the page or check if you get the error in an incognito window. If issue persists, contact support on a live session for further assistance.
The validation rule will not execute if the Field permission is set as read-only for any user profiles. If the issue persists even when the field and other access permissions are available, contact support with the validation rule ID, record ID, and a screenshot showing the issue details for further assistance.
Check if there are any field permissions or layout rule configured that blocks the validation action, or if the record is undergoing any blueprint transition. If there is no clear cause found, contact support for assistance.
Check whether the record is shared with the respective user via Data sharing settings with View only permission. If sharing is not specified, check the field permission for that profile. If the field permission is disabled, the user cannot edit the fields even when they are added under Fields allowed to be modified in the record-locking feature.
Verify whether the record is shared with the user via Data Sharing Settings with View only permission. If no sharing exists, check the field permissions for the user's profile.
Note: If a field is disabled for that profile, the user cannot edit it even when it's listed under Fields allowed to be modified in the record-locking feature. Additionally, if the record criteria is not satisfied, it will be unlocked automatically.
Record Locking only works for the approved records, not for the rejected record like the same applies for the record entering the blueprint process.
For issues related to buttons with function, first try executing the function manually and check if there is any error. If it works on manual execution and doesn't work when you click on the function, then contact support.
Open a record, click the Buttons dropdown, and drag to rearrange the buttons. If you have any trouble while doing so, contact support for assistance.
Check whether the user has permission for the button.
If the customer has permission and the issue persists, contact support. If the profile name doesn't show up when added to the permission, contact support.
The custom button associated with any related list, make sure you select the records from the related list to have the button be visible. If it still does not show, contact support for assistance.
When there are third party web links associated in the webtabs, these websites restrict their content from loading inside another website to avoid click-jacking attacks. They use the X-Frame-Options HTTP response header to indicate whether a browser should be allowed to render a page in an iframe.
Here is the link for your reference
Check if the user has the required profile permissions in both the CRM and analytics end. If the issue persists, connect with support to check by connecting on a live session and get assistance.
The X-Frame can be disabled from the Zoho Sites end. However, if your subdomain includes Zoho sites, then it is not possible to remove the X-Frame. You will need to have a custom domain for which we can disable the X-Frame.
Use https:// instead of http://. When opened in a browser tab, both work, but the CRM loads web tabs as iframes. Because Zoho CRM uses https://, loading an http:// iframe causes a security error, so the iframe URL must use https://. If the problem continues, please contact support and share screenshots or a screen recording and the URL you used in the WEB tab for further assistance.
CORS (cross-origin resource sharing) error occurs when a webpage requests a different domain and the server blocks the request because the Origin header isn’t allowed due to the website provider being restricting the request. Please contact your provider for further update on this.
This is a notification message that appears when the user tries to edit a Global Set Picklist field values in the layout field Edit Properties option.
If you need to edit the options of a Global set - Picklist field, navigate to CRM Setup > Customization > Modules and Fields > Global Sets and edit the respective values. If you have any trouble through these steps, contact support for assistance.
Check the fields and the associated Global set and if you are looking for any assistance contact support.
First, check if the Deal record you are creating is on any custom Layout. If yes, check if there is a pipeline setup for that custom layout.
If there are no pipelines created for the custom Layout, create one to find the Pipeline field to be shown while creating a Deal from each respective layout. If you have any trouble, contact support for assistance.
Currently, editing the Pipeline in the record view is not supported, unlike Stage or other fields.
As a Pipeline field works similarly like "Map Dependency Fields". Pipeline is like a parent field, while Stage is like a child field. The options shown in "Stage" will depend on the value in the Pipeline field. Contact support for any other questions.
Ensure that those Stages are added under the respective pipeline.
Navigate to Setup > Customization > Pipeline, choose the respective layout, check in that Pipeline, then Add the required stages and click Save.
Update the stage in the record view page or edit the record, then save by modifying it to any other Stage and check if it was updated and saved. If yes, and you still find trouble in updating the records only in the Kanban view, contact support for further assistance.
Compare the Stage values included in the respective Pipelines to then check if there is any 'Map dependency' set up for this Stage field as a Child file due to which the values listed will depend on the Parent value selection. If the issue persists, contact support for further assistance.
The Unaccounted option is not a pipeline. Records also turn Unaccounted when they were deleted from a pipeline or never assigned to one, when they were previously associated with a pipeline but later removed, or when a stage value added to the Deal layout is subsequently removed.
Currently, this is a limitation from our end, where custom pipelines won't be listed within the Convert action.
As a workaround, we suggest the following:
Create a picklist field in Lead Module with the same values as in your Custom Pipelines.
Map this picklist to the Deal Pipeline field during the conversion process This ensures the value selected in the Lead record automatically updates the Pipeline field on the new Deal.
Try to move the components one by one and check it. If it is a fluid component, try to switch to a fixed component and vice versa per your requirements. Move each component and try to fix the issue through trial and error method. If you have any difficulty with this, please connect with support for further assistance.
Currently, it is not possible to set a fixed state of a component while scrolling up and down in Zoho CRM canvas view.
Go to Canvas assignment on the setup page and check if the corresponding layout is mentioned and associated with the canvas view as default. If the issue persists, contact support for further assistance.
Go to Portal Tab Configuration under CRM Setup > Portal Configuration to see if the canvas view has been associated. If so, change it to default to release the Canvas association, after which it will be available to delete. If the issue persists, contact support.
Embedding the Zoho CRM calendar on the CRM homepage dashboard is currently not supported. However, it should not be necessary, as you can access it anytime via the Calendar icon located in the CRM top bar.
If you would like to embedded a calendar on the home page, then try using Zoho Calendar (instead of the CRM app calendar) using a widget.
In order to get appropriate guidance, please contact support connecting on a live session along with these details like, the profile permissions, the component name, and the home page name and ID you are facing trouble with for assistance.
Although records can be sorted in a custom view from the home page component, the sort order doesn't stay constant. Upon refreshing the page, it gets reversed and unsorted. However, this feature may be implemented at a later date.
There is no limit on creating a custom home. However, there is a limit to how many custom hom pages can be shared with each role or profile. A maximum of five custom home pages can be shared which includes adding 20 components per home page. Users can have up to 10 Home pages, including five per Role and Profile respectively.
Check if translation is enabled. If yes, the values will be shown based on the user's selected language in their personal settings.
Example: If you enable translations then rename a field, the new name is treated as the translated value. Users with CRM set to English (UK) will see the change; users set to English (US) will still see the old name.
You can translate the account’s picklist values to English as a one‑time, irreversible backend change. Before we proceed, we will need an email from super-admin sharing their consent to be sent to our support along with :
Only default picklist values for system (predefined) fields will be translated.
Custom fields and custom picklist entries won’t be changed.
If a default value was previously edited in a language, only that language’s default will be translated/updated.
Specify which English variant you require (US, UK, or other).
Currently, we do not have a feature supporting to show the current date in the email template.
Here is a workaround we suggest for this:
➤ Create a custom date field in the respective module.
➤ Create a custom function to update the date field with the current date.
Function: list = {1,2,3,4,5} for each item in the list.
{
Allleads = zoho.crm.getRecords("Leads",iter,200);
if(Allleads.size() > 0)
for each ele in Allleads
{
update = zoho.crm.updateRecord("Leads",ele.get("id"),{"Field_Name":zoho.currentdate.toDate()});
info update;
}
}
Replace the API Name in the above code.
➤ Associate the function with Schedules so it can be triggered automatically at 12 a.m.
➤ Add the custom date to the email template.
Check if the customer has selected the Send this notification as a Single Mass Email with all recipients displayed option.
If so, ensure that the email template does not contain an unsubscribe link. If the template has an unsubscribe link, it cannot be used for a Single Mass Email workflow rule.
As we allow adding recipients in CC: and BCC: in Single Mass Mail, we do not permit the inclusion of the Unsubscribe option.
It will take 24 hours to update the stats. If the stats are missing after 24 hours, then it could be that the customer has made changes to the template and hasn't sent any emails yet. If an email is sent before modifying the template, those stats will not be visible here.
If you want to view the stats for the older version, click on the template, then go to Analytics > Versions and check the stats.
All inventory modules require users to select a template before sending the email after clicking the send mail button. Users must have print preview permissions enabled to avoid this error.
If you missed adding the tag for the line items subform in the HTML code, the line items will not be visible. You need to include the following tags in the table element source code for the line items table:
<tbody id="subform_Subformname"> and </ tbody>.
Please contact support by joining a live session for further assistance.
Currently, this is a known limitation on our end. As a workaround, we suggest creating a custom lookup in the Products module to Deals module which would list in the Child module drop list. Custom - Products lookup can be used in kiosk.