Good Day Community
I´m trying to export several custom fields using the “Export Customizations” option but when i install the package in my production instance only the labels are created but no the fields.
For example, I created a field named “Brands” and the label is LBL_BRANDS in a Sandbox instance and when exported to Production only appears created the label but not the field, and in the layout only appears the name of the label LBL_BRANDS so I understand that the relation is working correctly but only the field is missing.
Do you have any suggestions as to what I might be doing wrong?
Thanks!
I have the same issue, when creating, export and importing new field in 8.4.2 field is not created I see it only in the label in list.
When I tried to import old customization from 7 ver field was created
onlye
11 December 2025 18:08
3
Same issue today with 7.14. Custom Labels are there in Studio and Labels appear in the edit view. But the custom fields are not in the Studio Fields and there is not input field by the Labels in Edit View. I am using for Contacts
Hello,
this is true. There are two issues pointing into the same direction:
opened 03:32PM - 25 Jul 24 UTC
Type: Bug
Priority:Critical
Area: Studio
Status: Team Investigating
Severity: Major
### Issue
Repair & Rebuild is not syncing vardefs with DB.
I exported cust… omizations form one install to another. Imported the changes. The vardefs/metadata and language files came over. In fact the front end editview/detail view came over. Upon further investigation the fields are not in studio and have not been created in the _cstm table for the module.
There are no obvious errors in the log or php log.
### Possible Fix
_No response_
### Steps to Reproduce the Issue
```bash
1.Add custom fields to one install of SuiteCRM 8
2.Export them from studio
3.Import them with module installer to a new SuiteCRM install
4.Do an R&R (confirm all vardefs sync'd with DB)
5. See no vardefs are sync'd with the DB.
...
```
### Context
In an immediate context, the export/import customizations feature in Studio does not work. However, in a larger context, R&R is not working as expected and not syncing vardefs with the DB.
So the vardefs are not being sync’d with the DB. So I don’t think its and angular thing.
The have been copied to:
…/public\legacy\custom\Extension\modules\Project\Ext\Vardefs\
I can also see them here:
…\public\legacy\custom\modules\Project\Ext\Vardefs\vardefs.ext.php
But not in DB, and not in Studio.
Leads me to believe the R&R is not working properly in SuiteCRM 8 to sync the vardefs with the DB.
### Version
8.6.1
### What browser are you currently using?
Chrome
### Browser Version
_No response_
### Environment Information
PHP 8.2
### Operating System and Version
Centos 7
opened 02:29PM - 04 Nov 24 UTC
Type: Bug
Priority:Important
Severity: Major
### Issue
On Adding a custom Field on a Module, like Accounts, not all Properti… es of the Field are written at
\custom\Extension\modules\Accounts\Ext\Vardefs
On Adding Field "KundenNr" on Accounts Module, the File "suitecrm_data/public/legacy/custom/Extension/modules/Accounts/Ext/Vardefs/_override_sugarfield_kundennr_c.php" looks like:
````
<?php
// created: 2024-11-04 10:26:17
$dictionary['Account']['fields']['kundennr_c']['required']=true;
$dictionary['Account']['fields']['kundennr_c']['merge_filter']='disabled';
?>
```
### Possible Fix
_No response_
### Steps to Reproduce the Issue
```bash
1. Add a Field on Accounts Modul
2. View the Extansion File at: \custom\Extension\modules\Account\Ext\Vardefs
3.
...
```
### Context
On Exporting changes on Studio an Importing on another Installation the Fields are not added on Targetsystem like reported her: https://github.com/salesagility/SuiteCRM-Core/issues/532
### Version
8.6.2
### What browser are you currently using?
Chrome
### Browser Version
Version 130.0.6723.69 (Offizieller Build) (64-Bit)
### Environment Information
MariaDB, PHP 8,2
### Operating System and Version
Windows 10
blqt
12 December 2025 09:17
5
I had found a workaround for that with SuiteCRM 7.
It’s likely it will work with SuiteCRM 8:
Create a subfolder named language under custom/modules/XXX
Example : for fields created for Contacts in SuiteCRM 8, create the folder
public/legacy/custom/modules/Contacts/language
Then try to export your module
Hello Benoit,
great finding!
Just tried it on a 8.9.1 instance and it’s working right away.
Do you have a github account? Want to add your finding to the issue?
opened 03:32PM - 25 Jul 24 UTC
Type: Bug
Priority:Critical
Area: Studio
Status: Team Investigating
Severity: Major
### Issue
Repair & Rebuild is not syncing vardefs with DB.
I exported cust… omizations form one install to another. Imported the changes. The vardefs/metadata and language files came over. In fact the front end editview/detail view came over. Upon further investigation the fields are not in studio and have not been created in the _cstm table for the module.
There are no obvious errors in the log or php log.
### Possible Fix
_No response_
### Steps to Reproduce the Issue
```bash
1.Add custom fields to one install of SuiteCRM 8
2.Export them from studio
3.Import them with module installer to a new SuiteCRM install
4.Do an R&R (confirm all vardefs sync'd with DB)
5. See no vardefs are sync'd with the DB.
...
```
### Context
In an immediate context, the export/import customizations feature in Studio does not work. However, in a larger context, R&R is not working as expected and not syncing vardefs with the DB.
So the vardefs are not being sync’d with the DB. So I don’t think its and angular thing.
The have been copied to:
…/public\legacy\custom\Extension\modules\Project\Ext\Vardefs\
I can also see them here:
…\public\legacy\custom\modules\Project\Ext\Vardefs\vardefs.ext.php
But not in DB, and not in Studio.
Leads me to believe the R&R is not working properly in SuiteCRM 8 to sync the vardefs with the DB.
### Version
8.6.1
### What browser are you currently using?
Chrome
### Browser Version
_No response_
### Environment Information
PHP 8.2
### Operating System and Version
Centos 7
blqt
15 December 2025 10:31
7
Done.
I also mentioned that the problem also exists in SuiteCRM7
1 Like