What is missing in my custom field vardef?

Hi,

I recommend to only create a basic definition and then update it after the repair

$dictionary['Currency']['fields']['c_primary_key_c']['name']='c_primary_key_c';
$dictionary['Currency']['fields']['c_primary_key_c']['vname']='LBL_C_PRIMARY_KEY_C';
$dictionary['Currency']['fields']['c_primary_key_c']['type']='int';

it's also better to name your file sugarfield_<thenameofyourfield>.php so it won't create another field after the repair (that can cause mistake with contradictory parameters) ; in my opinion, you can also avoid the _c because your field won't be considered as a custom field (not created from the studio) so it won't be store in the _cstm table but in the core one.

Fred

I ESPECIALLY want it in the custom table, that is why I defined the source (as per sugar documentation).

OK ; did you correct your type to int instead of Integer?

Yes, no luck. This is how I tried:

$dictionary['Currency']['fields']['c_primary_key_c']['name'] = 'c_primary_key_c';
$dictionary['Currency']['fields']['c_primary_key_c']['vname'] = 'Dimensions key';
$dictionary['Currency']['fields']['c_primary_key_c']['id'] = 'c_primary_key_c';
$dictionary['Currency']['fields']['c_primary_key_c']['type'] = 'int';
$dictionary['Currency']['fields']['c_primary_key_c']['dbType'] = 'int';
$dictionary['Currency']['fields']['c_primary_key_c']['source'] = 'custom_fields';
$dictionary['Currency']['fields']['c_primary_key_c']['len'] = 10;
$dictionary['Currency']['fields']['c_primary_key_c']['size'] = 10;
$dictionary['Currency']['fields']['c_primary_key_c']['unified_search'] = false;

I tried on my instance and with your full definition it is not working.

If you just put the 3 lines and accept the field to be created in the core table, it works.

2 possibilities

- the currency module canno't manage a _cstm extension table

- the table must exists in order to perform the repair (I got error message in the sugarcrm.log with your definition)

It is paramount to put into the _cstm table. SugarCRM itself announced us in a in-house webinar (they visited our company) that sometimes they upgrade core table structure by copy, drop table, create, copy from clone back, instead of alter table. And in general is bad practice to put custom fields into core table. One of the reasons why I am rewriting our entire codebase is to rip out the custom fields from the core table. Should I go to sugar portal and contact them?

It is paramount to put into the _cstm table. SugarCRM itself announced us in a in-house webinar (they visited our company) that sometimes they upgrade core table structure by copy, drop table, create, copy from clone back, instead of alter table. And in general is bad practice to put custom fields into core table. One of the reasons why I am rewriting our entire codebase is to rip out the custom fields from the core table. Should I go to sugar portal and contact them?