How does SuiteCRM V8 handle database schema modifications when extending core modules?
I think it handles same as v7.
Custom fields are stored in separate tables with a _cstm suffix. For example, custom fields for the Contacts module are saved in a contacts_cstm table.
Yes this is correct.
The next logical question is in the past we modified one of the *def files, ran a repair and rebuild and the table with relevant columns were created.
Just to confirm, we use the same structure / same process even though we work with Symfony framework now, right?
I was questioning the same, i will try it on our Dev Machine and will comeback with hopefully good news 
Hey so i tested and got a stunning result:
When Running the Quick Repair and the end returns this message:
If i press Execute it will create the field in the Accounts Table on mysql and not Accounts_cstm @rsp
Not sure this is how it should have worked but hey, this fixes a lot of my problems on Leads Conversion for example:
I need to create a original field for Industry to pass the fields when converted, this fixes a big workaround that we implemented using workflows.
Hope i clarified it well XD
Yes this is something that months ago I came across also.
Though with the old V7 if you install a custom module from a zip file I had all the columns and tables auto generated
Oh my tests where done in V8.8.0, never touched V7 so cannot check it out 
Okay thx.
Some other ‘plan’ is likely needed then.
1 Like