Forum Moderators: phranque
Any suggestions? I need to have a better way to store and utilize this data than seaching through e-mails!
Unfortunately, I have a couple of custom fields (Arrival Date and Departure Date) that I can't readily drop into an available Outlook field. Outlook's built-in importer won't map to custom form fields. :( That's why I'm looking for a custom import solution.
I could just put the Arrival Date and Departure Date in the notes field (that would work fine for my purposes) but I can't find a way to map both database fields to a single Outlook field, and for the sake of a simple form I need those two values to be entered separately.
"11/11/2002","11/13/2002"
you would need to remove the "," part:
"11/11/2002 11/13/2002"
That will allow you to import the two dates into one field. Sticky me if you are having additional issues or want me to take a look at the import file.
I am also trying out a couple of programs that will semi-automate the import to Outlook (using Outlook's built in converters, I have to map the fields every time I import). ContactGenie claims to both remember mapping settings for a particular database and also to also overcome the problem with importing into custom forms in Outlook.
I always like to have more than one option, though, so if you can think of any other ways to simply get the data from my .csv file into Outlook (since I will be doing this every day) I would appreciate the input.
Thanks for all of your help!
In theory it should be possible - Run a script in ThisOutlookSession::Application_NewMail() check the subject of the mail, if it applies create an instance of your custom form and set the properties by parsing the bodytext of the new mail item.
Let me know if it works, I could use a similar solution myself :)
Let me know if it works, I could use a similar solution myself
I've got a better idea - you write the script, and let me know if it works :) You will note my nickname has no references to code ;)
Actually, I'm still working with CaTrap, which should do exactly what I want from within Outlook (it is an add-in) - the author sent some helpful material to me that might get me back on track.
I guess the problem will be that I want the data in Outlook to make contact management easy, and I want it in a database to make bulk e-mailing (or mailing) easy. I did see one solution that let Outlook use an access database (rather than a .pst file) as the source for contacts - that would really simplify things. It was not inexpensive for more than 3,000 records, however - that was the drawback. So I did not even try it out.
Andreas
Interesting note - it seems that CaTrap will also let me export to a database file by setting up another rule in the Outlook rules wizard. So if that works, I could get a new inquiry form, automatically parse all of the relevant data into Outlook, then (again without any user intervention) export to a database file. I really like the "no user intervention required" part of this scenario.
My reason for wanting the database file is flexibility if I later want to do mail merge or e-mail merge to my contacts. I don't think Outlook is a suitable vehicle for either :(
I'll post later if I get this all working as planned.
Now I just need to implement this for some of my clients so I can bill out the time I've spent figuring all of this out :)
Now I want to get the database export feature of CaTrap working at the same time. I am almost there - I'm just having some trouble with fields where customers are putting commas and messing up my de-limiting. Perhaps a switch to tab-delimited (rather than.csv files) might do the trick. But its getting late!
Well worth the effort, it is a very, very usefull feature for Outlook - no more online db's for my web enquiries juast good ol plain text email. Thanks for the inspiration to get off my a** and do it :)
The parsing just just needs the email to be plain text like this:
first=john
last=smith
email=johnsmith@hotmail.com
Referrer=google
k1=cheap
k2=widget
is read by outlook like this:
myCustomContactItem.UserProperties("Referrer") = parse( "Referrer", myWebEnquiry.Body )
So why do you want to export them now to a database?