SeedCodeCalendarComplete

Import Or Export Vcard

Exporting vCards

You can export either a single vCard or a found set of vCards. In either case, exports are done from the table view of the contacts tab; to get there, click the "table view" icon.

In the upper right of the table view layout you'll see a button for exporting vCards. Once you click this button you'll be asked if you wish to export one contact or the found set of contacts.

Exports are automatically placed on the Desktop and named FirstNameLastName.vcf for single contacts and Xcontacts.vcf for found sets. You can change this naming scheme by editing the SetVariable $Path statement in the "Export vCards" script.

Changing the Export Content

If you want to change the actual information being exported (if you've added some fields to the contacts database that you'd like to include in your vCard, for instance), you'll find this pretty easy. You simply have to edit the z_ContactVCARDCalc field in the Contact table. There are some custom functions used in this calc, but don't worry about them because they are just behind the scenes things: the actual fields being exported are right there in the calc for you. Note that portions of this export reside in other tables so you may want to look at or modify the z_AddressVCARD_Calc field in Address and the z_PhoneVCARD_Calc field in the PhoneFaxEmail table.

Synching (this doesn't work)

Unfortunately, this import and export of vCards was not designed to synchronize two sets of contacts. It is intended to let you more easily move contacts into and out of SeedCodeContacts, but not to keep SeedCodeContacts in synch with changes made on another device.

Missing the seedcodeVCard.xsl file?

If you're seeing this error when exporting vCards, it is likely that you moved SeedCodeContacts without moving the vCardXML folder that came with it. The seedcodeVCard.xsl file is in that folder. Simply place this file wherever you'd like (you can even place it on your web server and reference it with a url) and then change the reference for it in the "Export vCards" script in SeedCodeContacts. (You change the reference in the "Export Records" step near the end of the script. Click "Specify" next to "Specify Output File" and then click OK to get the XSL Options Settings.)

Importing vCards

Limitations

There are a _lot_ of varieties in vCard formats. This import attempts to deal with all of them and supports multiple addresses, multiple phone numbers (and emails, faxes, cells, etc.), "primary" numbers, as well as phone and address labeling. It even tries to put things it doesn't understand in to the contact's notes field. However, you may well encounter vcards where this import may not extract all the information and may not label all the phone, fax, and email entries as they were in the vCard. In such cases you may need to modify our import script do accommodate your circumstances.

The script is very modular and tests each line of the vCard before setting the results to variables (things like $phone, $address, etc.). When the script finds that it has gathered an entire vCard it then creates a new contact record with these variables, creating related phone, fax, email, and address records as needed. We hope you find this script straightforward and easy to modify.

Importing

You can find the button to begin vCard imports on the Import section of the Admin tab.

Note, SeedCodeContacts doesn't do any dupe checks on the incoming records, so while it will not overwrite an existing record, you may import a duplicate. See flagging duplicates for more information.

After you begin the import you'll be asked to select your vCard file. The script will have this import set to "Store only a reference" to the file: be sure to leave the setting that way.

Importing these files can take a while, but you'll see each contact appear in the contact list as it is created, letting you know that the import is working. You can stop the import at any time, but you can't restart from where you left off. You'll have to begin the import again.

(855) SEEDCODE
[email protected]
Follow us: