Importing contacts: Difference between revisions

Assume that we start with a spreadsheet that has column headings matching the 17 fields shown below.  Assume too that we want to capture all of the data in the sample.  (The owner of the data collected it for a reason and they wouldn't be too happy with a loss of data in a migration to a new application!)  I did not define new fields in the database, but I did correlate my data source to the Accounts and Contacts tables.  Because I had parsed the data source (spreadsheet or CSV file) for column headings, I simply exported that variable and then used it as a comment right in my code workup as I went.  What I mean is that I created a PHP (array) variable of the 17 field names, and then used the [http://php.net/var_export|var_export]() function to print it and copy/paste into a comment block so that I could mark up a plan for mapping those fields into fields in SugarCRM.

print '<pre>'; var_export ($arrFields); print '</pre>';

// copy and paste that output; then add comments about which fields go into which table

   16 => 'ticker_symbol'// a:ticker_symbol                   

)

=== Using a Form ===

; Tip: You can peer into the SugarCRM environment with a call to PHP's 'get_defined_vars()'.  This will give you some information about field maps etc.

# temp.php to show a concise view of the variables defined in the config script

define('sugarEntry', true);

                     [Website] => website

                 )

== Using SOAP ==

Even more detail can be had by inspecting the service.

$get_available_modules_params = array (

   'session' => $session_id,

// output:

See [[Importing_contacts/sugar_modules]]

$interestedModules = array('Accounts', 'Contacts');

   print "\n $module_name fields:<br />\n<pre>\n"; var_export ($result); print "\n</pre>\n";

}

===Accounts fields: ===

== Setting Records ==

// read in our data from source CSV file format

$arrData = file('./account_contact_list.csv');

   */

}

== Conclusion ==