function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Kate Starostina 13Kate Starostina 13 

Need some ideas on Contact design

I have a group that I am on boarding to our SF instance.  They mainly have Contact data that contains primarily 5 fields of important contact data which includes Level, Discpline, Sector, Speciality and Sub Specialty.  They use these 5 fields to set filters to run reports for email campaigns and physical samples they need to send out.  The main issue is that these fields in their system are multi-select.  I don't want to create 5 multi select fields for them because reporting would be diffficult.  Any ideas on how to get this working with the least amount of fields and avoiding multi-select?
GauravGargGauravGarg

Hi Kate,

If you are moving data from one system to SF and user's are going to interact with the system, then it is advisable to create the same set of fields which are available in exisitng Database. 

This would not be a problem also would be easy for you to maintain data integrity as well as user's won't need training to utilize new org. 

Thanks,

Gaurav
skype: gaurav62990
Support: gauravgarg.nmims@gmail.com