Importing works for all the existing imports in salesboom:
Opportunities, Accounts, Leads, Contacts, Contracts, Products and
Tasks.
The user interface for importing basically remains unchanged for
the first two steps.
- uploading a CSV file and
- mapping the columns in the CSV file to salesboom's columns.
After mapping the columns, a summary screen will be displayed listing
any Errors that occured when Salesboom was checking over the CSV
file you uploaded. If the user decides to continue with their import,
they just click the "Import Now" button.
Here is a list of Errors that are flagged.
- Selection Lists:
e.g. Lead Source when importing Accounts. (If you put an invalid
value for the column "Lead Source" in your CSV file,
like "blahblah", you will be warned on the error summary
screen.)
- Empty Required Fields:
If a field shown in red on the mapping screen is empty
- Numeric/Money fields
Entering invalid numbers for currency/numeric fields: e.g. Amount
under Opportunities
- Boolean:
valid values for boolean fields. (e.g. "Active" in Contacts)
are: true,t,yes,on (true) or false,f,no,off (false) NOTE: these
are case insensitive, and it's easy to add more
- Integer fields:
e.g. "Percent Complete" under Tasks - Values must be
a valid integer.
- Lookups (linking salesboom objects):
- - e..g fields like "Account" and "Contact" when
importing tasks.
- For linking contacts you would like a Task to a Contact by
giving the name in the form "John McDonald" in your "Contact" column
in the CSV file. (This is how sf does it.) I just realized
I should probably use something in adition to just the contact
name to better distinguish between Contacts (e.g. two John
Smith's), but I can fix this quickly sometime next week
- To link accounts, use the Account name. (e.g. "asdf")
- Text
Text that is too large to fit in the database column is cut off
to fit by default. (this is obtained from the database so if
we change a column attributes, Importing will be updated automatically.)
For everything but Text, the default operation is to leave the entry
blank on insert if an error is encountered. (so if the user has an
invalid "Percentage Completed" for a Task in their CSV
file, none will be inserted for the record with the problem.
If you are missing a column for a record, an empty one is created
on import.