Help with custom fields in multiple modules

[eddt]

I'm not really having a problem with anything, meaning my install is working just fine. However, I'd like to add a custom field to a module, and have it "span" across multiple modules. Simply, I've added a text (varchar) custom field to the "Contacts" module for the Company Name. I've set it up in all the requisite views for that module, so its working fine, and is readily viewable and editable in "Contacts".

Now, I'd like to be able to have that same value carry over into and show up in other modules. So that when I go to the "Accounts" module, it has the same field in it. That way when we "convert" a Contact into an Account, their Company Name value show up on the Accounts side. But when I look at the Accounts module in the Studio, there is no way to add my existing Company Name field, since its apparently for the Contacts module only.

I guess my question is am I just not thinking here? Am I not seeing something simple that I have to do to tie the data into both modules? Do I just make another Custom Field in the "Accounts" module that has the same name as the one in the "Contacts" module? Is it some other arcane trick of programming I need to perform? Any help would be appreciated - I've scoured the forums and the wiki for the past few hours and learned a few new things, but not regarding my issue, so I thought I'd go ahead and ask!

FreeBSD 6.2 Shared hosting server - SugarCE 4.5.1g - Apache 1.3.37 - PHP 4.4.7 - MySQL 4.1.21

[jli]

in order to conceptually have one field in one module carry over to other modules, you'll have to recreate the same field in the other modules, and possibly code why/when one field value would carry over to the other module(s). there is not automatic way to do this in Sugar using the Studio or other parts of the admin features.

[kuske]

Have a look to thread Global custom fields

hk

[eddt]

Jli and Kuske - thanks for the input/feedback! It looks like the thread Kuske pointed to addresses my issue, and I'll give that method of using a global custom field a try!