OutlookEX UDF - Help & Support (II)

[Mun]

Is there no alternate way to the pseudo clicking through additional .exe?

[water]

Only alternative is to have a current anti virus programm installed so Outlook sees no need to pop up the warning message.

[HighlanderSword]

Hello,

Is their any way to resolve the Dispal name of an email address ?

For Example Dg - Test is the display name and the full email address is dg.-test@resolveme.com

When i try and use _OL_ItemRecipientCheck it is not able to resolve the Display name to get the email address.

The display name is a Dg Group and is valida inside of  my organization.

I'm trying to give users the options to user either the Display name or fully resolved email address.

If I use the full resolved email address the function does resolve it to the display name.

Please let me know

[water]

_OL_RecipientCheck should return the displayname in element 6 of the returned array. What do you get?

[GreenCan]

Hi water,

I am trying to import contacts in Outlook 2010 using your slightly modified example script

#AutoIt3Wrapper_AU3Check_Parameters= -d -w 1 -w 2 -w 3 -w 4 -w 5 -w 6
#AutoIt3Wrapper_AU3Check_Stop_OnWarning=Y
#include <OutlookEX.au3>

; *****************************************************************************
; Create test environment
; *****************************************************************************
Global $oOutlook = _OL_Open()
If @error <> 0 Then Exit MsgBox(16, "OutlookEX UDF", "Error creating a connection to Outlook. @error = " & @error & ", @extended = " & @extended)
Global $Result = _OL_TestEnvironmentCreate($oOutlook)
If @error <> 0 Then Exit MsgBox(16, "OutlookEX UDF - Manage Test Environment", "Error creating the test environment. @error = " & @error & ", @extended = " & @extended)

; *****************************************************************************
; Example 1
; Import all contacts from c:\temp\_OL_ItemExport.csv to
; *****************************************************************************
Global $iResult = _OL_ItemImport($oOutlook, @ScriptDir & '\Test.csv', ",", "", 1, "*\Outlook-UDF-Test\TargetFolder\Contacts", $olContactItem)
;~ If @error <> 0 Then Exit MsgBox(16, "OutlookEX UDF: _OL_ItemImport Example Script", "Error creating contacts from file @ScriptDir & '\Test.csv' in folder '*\Outlook-UDF-Test\TargetFolder\Contacts'. @error = " & @error & ", @extended = " & @extended)
;~ MsgBox(64, "OutlookEX UDF: _OL_ItemImport Example Script", $iResult & " contact(s) successfully imported to folder '*\Outlook-UDF-Test\TargetFolder\Contacts'.")
If @error <> 0 Then Exit ConsoleWrite("OutlookEX UDF: _OL_ItemImport Example Script" & @CR & "Error creating contacts from file @ScriptDir & '\Test.csv' in folder '*\Outlook-UDF-Test\TargetFolder\Contacts'. @error = " & @error & ", @extended = " & @extended)

ConsoleWrite("OutlookEX UDF: _OL_ItemImport Example Script" & @CR & $iResult & " contact(s) successfully imported to folder '*\Outlook-UDF-Test\TargetFolder\Contacts'." & @CR)

_OL_Close($oOutlook)

As you can see in the script, I import a csv in $olContactItem

The csv file looks like this example (manual import works fine)

Name,Mobile Phone,Business Phone,e-mail
Mr X,+32586666669,+32477412872,ACL@whoompie.be
Ms Y,+32477412872,+32586666669,ADE@whoompie.be

But when I proceed with the script, something unexpected happens. Instead of creating a test folder in 'Contacts', Outlook creates some folders in 'My calendars' (Outlook-UDF-Test, SourceFolder, Calendar, TargetFolder and Calendar)

Only the first Calendar folder contains some apparently garbage data (TestAppointment, Building A, Room 10, during 2 weeks...!?), All other folders are empty.

When i remove the Outlook-UDF-Test folder, all other folder are deleted all together.

The first thing that I see after running the script is a test-appointment Conflict popup.

This is the error that I get:

COM Error Encountered in _OL_ItemImport.au3
OutlookEx UDF version = 0.9.0
@AutoItVersion = 3.3.8.1
@AutoItX64 = 0
@Compiled = 0
@OSArch = X64
@OSVersion = WIN_7
Scriptline = 1211
NumberHex = 80020009
Number = -2147352567
WinDescription = 
Description = The attempted operation failed.  An object could not be found.
Source = Microsoft Outlook
HelpFile = 
HelpContext = 0
LastDllError = 0
========================================================
OutlookEX UDF: _OL_ItemImport Example Script

Error creating contacts from file @ScriptDir & '\Test.csv' in folder '*\Outlook-UDF-Test\TargetFolder\Contacts'. @error = 7, @extended = 100!

I am running Outlook 2010.

Obviously, error in line 1211 with error 7 indicates that $vFolder (expected: "*Outlook-UDF-TestTargetFolderContacts") is not recognized as a valid object.

The issue is that $vFolder is empty ("") because $aTemp = _OL_FolderAccess($oOL, $vFolder) returns an array with an empty element 1.

[0]|5
[1]|
[2]|2
[3]|0000000038A1BB1005E5101AA1BB08002B2A56C20000454D534D44422E444C4C0000000...

[4]|000000007E87175E3BE86642A9828040F7DFFA5801004BC99E6BE5B80B459D5F1D58A5C...
[5]|\\myemail@addressOutlook-UDF-Test\TargetFolder\Contacts

Any suggestion, hint how i can fix the issue?

thanks

Greencan

[water]

Hi GreenCan,

the "problem" you see is caused by line

Global $Result = _OL_TestEnvironmentCreate($oOutlook)

This creates the test folders and populates them with some example items. This is so that other functions have a defined environment to play with.

If you run _OL_TestEnvironment you can manually create/remove the test folders.

To create the items in a test folder of your Contacts folder use something like:

Global $iResult = _OL_ItemImport($oOutlook, @ScriptDir & '\Test.csv', ",", "", 1, "*\Contacts\Test", $olContactItem)

and make sure the folder exists before running the import.

[GreenCan]

the "problem" you see is caused by line

Global $Result = _OL_TestEnvironmentCreate($oOutlook)

I overlooked this, I removed the line as not applicable for my test.  thanks

To create the items in a test folder of your Contacts folder use something like:

Global $iResult = _OL_ItemImport($oOutlook, @ScriptDir & '\Test.csv', ",", "", 1, "*\Contacts\Test", $olContactItem)

and make sure the folder exists before running the import.

OK, i did this but the script still failed with @error 7

It took me a while, but by debugging line by line, I found that the issue was in the header of the csv file.

__OL_CheckProperties returned @error 100

Name did not match any of  the items in $sItemProperties

I had to replace the header row

    Name,Mobile Phone,Business Phone,e-mail

by 

    FullName,MobileTelephoneNumber,BusinessTelephoneNumber,Email1Address

I must say that I am pretty confused because manual import works fine with the first header, but scriptwise doesn't work.

And if i change the header to the second one, then scriptwise import is OK but manual import does not work.

For example, I have to remap FullName to Name.

is this a Microsoft joke?

At least my issue is solved now....

Thanks

GreenCan

PS Where Can I find an enumeration of all the Item Properties?

[water]

GreenCan,

all ContactItem methods and properties for Outlook 2010 can be found here.

I will evaluate the other problem. It should either be a remark in the help file or the function should accept both formats.

Will post my findings here.

[GreenCan]

I will keep the url...

Thanks mate

Edited July 9, 2013 by GreenCan

[water]

I did some more investigation.

Here is a list of headers for manual import of contacts.

Here you can find how to create this list.

[GreenCan]

Thank you for the research water.

I will use your OutlookEx UDF to automate an Interface between an Oracle database (Crew Management System) containing the telephone numbers and E-mail addresses of our crews and supplier contacts (thousand records) and import the data into a shared Contact list.  Outlook contact links then back to our new Cisco UCAAS, using WebEx as Desktop Interface. Our Ops Control people dial from the Desktop and don't want to use the phone set to make some 200 calls a day.

It is important that any change in the Oracle DB is replicated ASAP into the WebEx environment.

It took me an afternoon to get a good idea how this will all fit together, thanks to your UDF. 

And I have no plans to do any manual imports .

[water]

Glad to hear that AutoIt and my UDF made it into such a professional application. And let's not forget WoolTown who wrote version 1 of the Outlook UDF.

[GreenCan]

of course...  Thank you WoolTown

[water]

I have added a remark to the Import function that property names are needed in the header line of the CSV file.

[orbs]

i think i have a core misunderstanding about something: when calling any Outlook method by COM, it is the Outlook application that actually performs the operation, and not the AutoIt engine that is running my script, right?

i mean, for example, if Outlook and my script are running in different security contexts, than the SaveAs method, which performs disk operation, is executed in the security context of Outlook, and not the security context of my script. is this correct?

thanks in advance for clarification on this point.

[water]

How would you create different security contexts?

[orbs]

specifically, i launch my script with RunAs with flag 2 (Network credentials only, the equivalent of cmd /netonly switch). so i get different security context on network resources.

now my script calls the SaveAs method by func _OL_ItemSave(), with the destination path being a network share, where my script has full access, but the user running Outlook does not have any access.

in this scenario, will the item be saved to the network share?

according to my tests, the answer is no. but for what reason? if my previous post assumes correctly, then this is obvious. otherwise, there may be an issue which needs to be resolved.

[water]

Is Outlook up and running when you call _OL_Open?

I think it matters in which context Outlook was started.

[orbs]

yes of course Outlook is running, otherwise i would not be able to open a connection to it.

the item is saved successfully on the following conditions:

- the destination path is local, where both my script and Outlook have RW access

- access to the network share is availabe to Outlook by manual authentication

so on "normal" conditions, no problem. issue occurs only in the condition specified in previous post.

[water]

yes of course Outlook is running, otherwise i would not be able to open a connection to it.

You would be, because the UDF connects to an existing instance of Outlook or creates a new one if Outlook is not running.

If it exists then Outlook runs in the user context. If the UDF = your script starts Outlook then it runs with the credentials specified with RunAs.

Could you please run your script when Outlook is not running at the moment?