Method Community

Hi

I am importing contact data into Method.

I have Job Descriptions (Buyer, Director etc) in my contacts file to import.  I have modified my Contacts screen to include the relevant field, however there isn't an option to map this field when doing the integration/Import.

How do I use this field, I don't want to create a duplicate field for this if I don't have to.

Thanks
Rick 

Hi Rick,

Have you added the custom fields to the Contacts table in Method? If not, you would need to do this first to be able to import the relevant data into these fields. 

You can do this by navigating to the Customize tab in Method, and clicking on the Tables/Fields tab link.

From here, scroll down until you see the Contacts Table and select Edit Fields...

Once you have gone ahead and added these fields, you should be able to import your Contacts file successfully.

Regards,

Ben

Hi Ben

It's not a custom field, it's the standard JobDesc field on the contact entity.  I have modified my screen, so that this field is displayed, but when I'm doing the integration I can't map the data.  A workaround would be to add my own JobDesc field to the contact table and then map, but I don't want to duplicate fields when there's probably a fix!

Thanks

Rick

Hi Rick,

The JobDesc field is unfortuantely not a field you can import data into via the contacts Table. This field is linked via the Entity table, and as such would require you to import directly into the Entity Table to populate data in this field.

This field is typically used to describe information regarding a Customer Job. For example, if you had a Customer named Jim, who you work with fairly often on a variety of different Projects that you wanted to keep separate, you would create a new Customer as a sub-customer of Jim for every new Project you did with him. On these sub-Customers, you would fill our the Job Information section to further specify What kind of work you are Doing for Jim.

It seems like what you are desctibing is the Contacts Job title at the company they work for is. I would recommend using the workaround that you described and creating a New field for this information.

Thanks Rick!

Regards,