- How To Import Blank Fields into Picklist Fields
- Posted by Ian on June 7th, 2004
Hi All,
I'm importing Contacts using the simple method (tools-
import-contacts-from file...).
Everything is going well except for little thing: I can't
seem to import blank data values as blanks. If I map the
blank data value to "Default Value", then "Default Value"
is literally imported (without the quotes).
Do I need to use the Data Migration Framework to get this
functionality? I don't want to go there, because I'm 96%
completed doing it the simple way.
Any suggestions?
Thanks,
Ian
- Posted by Andrew on June 8th, 2004
Hi Ian
Had the same problem
A simple workaround that worked for me is to map the blank field to "Default Value", import the Contacts and subsequently run a Manual Workflow to test for this and plug in "Null" when found
For multiple blank fields, set up dummy discreet values in the picklist/s to be imported to, map the blank fields to them and plug "Nulls" as above
Not elegent I grant you but ......
Hope this helps
Andrew Sage
- Posted by Matt Parks on June 8th, 2004
Another alternative would be to just update the tables directly after the Import
via SQL. Direct updates are technically not supported, but as long as you are
updating something basic (like a picklist), then there usually isn't any impact.
Matt Parks
----------------------------------------
----------------------------------------
On Mon, 7 Jun 2004 22:16:03 -0700, Andrew <asage@bigpond.net.au> wrote:
Hi Ian,
Had the same problem.
A simple workaround that worked for me is to map the blank field to "Default
Value", import the Contacts and subsequently run a Manual Workflow to test for
this and plug in "Null" when found.
For multiple blank fields, set up dummy discreet values in the picklist/s to be
imported to, map the blank fields to them and plug "Nulls" as above.
Not elegent I grant you but .......
Hope this helps.
Andrew Sage