Hi all,
What is the best practice to match a core Dropdown field between modules, when it only exists in one module OOTB?
I'm sure this comes up often enough, so wondering how others address this issue.
example; the Industry dropdown in Accounts is very useful, however it doesn't exist OOTB in any other module, i.e. Leads, therefore if you add industry_c into Leads using the same Dropdown it won't carry over during conversion.
If configuring a new Sugar instance, we simply create industry_c in Accounts module to solve this but on an existing instance where the OOTB field has been used for many years on thousands of records it would require a lot of work to both migrate the data from industry to industry_c field, and also update all the reports that use it.
I'd be very interested to hear how others manage this, and if Sugar product team has this field and others under consideration to resolve the issue?