05-10-18 11:50 AM
Answered! Go to Answer.
15-05-20 03:20 PM
I've been looking into this. Sometime within the last 12 months, there was a security fix applied which actively prevents this functionality from working on a shared mailbox. The code was previously tested on a non-o365 envrionment, so I'm wondering if that has something to do with it.
Google led me to a post confirming that the code in the VBO is what was previously valid, so it's not technically a syntax error.
I did find one work around, but it's a hack and a two-step solution. Do note that this will not take into account any value supplied for the subfolder variable, but does require that some value be present in order to trigger. The end result will pull from whatever the current active folder is, which somehow doesn't trip any security flags. I looked into setting the folder as the current active folder by code, but that uses the same code snippet that's currently running into issues.
Step 1:
Modify the Sub_Folder section of the code
If Sub_Folder <> "" Then if sharedEmail <> Nothing then folder = app.ActiveExplorer.CurrentFolder else For each name as string in Sub_Folder.Split("\") folder = folder.Folders(name) Next end if End If
Step 2:
Have a separate VBO attach to Outlook and click the subfolder that you want to access.
15-05-20 03:33 PM
15-05-20 03:53 PM
15-05-20 07:27 PM
16-05-20 07:53 AM
17-05-20 08:23 PM
18-05-20 03:52 PM
18-05-20 07:09 PM
28-07-20 06:25 PM
28-07-20 06:36 PM
If all you need is to pull mail from a shared mailbox on the same profile, then yes - I can confirm that the new version of the Outlook VBO does this.
As far as an extended object, not that I've seen specifically. There are a couple of alternative builds either on the DX or floating around on the communities that have been attached to posts that have one or two actions that the base VBO does not, but it's otherwise the same.
If you need to pull mail from another profile, like you would have in MAPIex, you'll need a copy of the VBO I posted elsewhere.