I am loading an Office.js outlook addin (hello-world-addin sample https://github.com/jasonjoh/hello-world-addin) in my web account. The addin seems to be working fine in my old outlook account. However, if i test it in new outlook account, the addin doesnt show at all the Incoming folder (email read). Does anybody knows how to solve that issue?
Related
I am building a custom add-in for outlook, but I couldn't use the add-in after adding to outlook, because it is inactive(disabled).
I created a custom add-in by following this documentation.
But after creating the add-in, I was not able to sideload using npm start.
So I used this. npm run dev-server.
And I added the add-in to outlook by following this guide - outlook on desktop.
At this moment, the custom add-in I just added is inactive, so I tried to troubleshoot this.
The documentation says I should go to File->Slow and Disabled COM Add-ins and enable the disabled add-in, but there were nothing in the option.
And also I tried to find add-ins in the system registry and set to enable always, but I couldn't find the added custom add-in either.
https://learn.microsoft.com/en-us/office/vba/outlook/Concepts/Getting-Started/support-for-keeping-add-ins-enabled
Did I miss anything or ...?
Even if the add-in is active, but it doesn't work.
I signed in with my work email and am using the latest version of Office365.
Thank you.
You are mixing web and COM add-ins for Outlook. It seems a web add-in was created using the yeoman generator and sideloaded into your Outlook account. Note, web add-ins work for Exchange profiles only (including O365). Most probably you are trying to run the add-in against a non-Exchange account in Outlook.
But the troubleshooting steps described in the post are related to COM add-ins only (VSTO based ones too).
We just released our Office JS Add-In for Outlook. Our Add-In takes one or more emails and sends them to an external web service to upload as a case note attachment for our enterprise application. With the previous Visual Studio Tools for Office (VSTO) technology, we could invoke our Add-In with any number of emails selected so that many could be sent at one time. With the Office JS technology, if we select any more than 1 email, the Add-In button is not enabled and we can't invoke our Add-In. We have 12,000 customers using this tool using VSTO and they will report this as a bug for our Add-In given that the old technology works and the new technology does not. We would like this capability added for Office JS so our customers can do what they did using VSTO.
This is not possible today. We track Outlook add-in feature request on our user-voice page.
It looks like the feature you want has been requested by others already. Please upvote the existing request https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/suggestions/11080962-allow-outlook-add-in-commands-to-be-used-on-select. Feature request on user-voice are considered when we go through our planning process.
I have a Client Project relationship in my web-app. I want to allow my web-app users to be able to file emails right from within Outlook. So in my Outlook Web Add-In, I want to create the client project folders on the fly, if they do not exist already, and move the selected email item in the respective project folder.
My code works fine in Outlook Windows. In Outlook Web, it executes without any errors, but the folders are not displayed. If I reload the web page, the folders are there and the email is in the right folder.
I have talked to Microsoft support and they are saying that OWA is working fine.
Can anybody help me spot any issues with my code?
CreateFolderPath EWS operation is not allowed in my add-in. So that does not seem to be an option.
The manifest file is available at https://newdev.timesolv.com/Integrations/addin/SimpleVersion.xml
This is a bug. It has been submitted to Microsoft and they have acknowledged it.
Update: On January 27th, 2020, the issue was closed by OfficeDev. I confirmed and it was working fine.
We are developing an Outlook Web App add-in.
Our Client dont want to see the add-in in outlook, in other words, they want to show the enabled add-in in owa only. is it possible to do that?
or is it possible to hide the add-in button in outlook?
This feature is currently not available. The good new is the officespdev.uservoice.com has confirmation from Microsoft that the request to allow mail apps to be OWA only is now in backlog and there is chance it will be implemented. Obviously you are welcome to upvote this request.
Now about options available right now as work around ...
The suggested work around by #NamigIsmayilov (Enable Outlook Web Add-in only on the Web) I wouldn't consider. This is possible, but the manifest crafted this way won't be accepted by Office store.
You may have a look on (How to detect if Office 365 addin is already active from a VSTO Outlook addin or vice-versa?) thread. This is about detection from VSTO/COM add-in, if you have one, web add-in and possibility to display some informational message to the user.
We've created an Outlook add-in which integrates our custom CRM with Outlook. A command button is added to messages in read and compose mode. A function file is called on the button click.
The add-in manifest passes validation and installs properly on all machines. However on Outlook 2016 desktop (only) we are seeing an error on some machines. The exact error message says: “We’re sorry, we couldn’t access [NCS Outlook Add-in]. Make sure you have a network connection. If the problem continues, please try again later.” ([NCS Outlook Add-In] is the name of our add-in.)
Note that this message appears IMMEDIATELY after clicking the add-in command button. It does not first say “[NCS Outlook Add-in] is working on your request” like it add-ins do when an error has occurred.
We have tried Outlook logging and haven't found anything useful in the logs. We've checked settings and disabled other add-ins. We have also tested across machines with user accounts. The same user will have the error on one machine and not the other. In short, it seems that the error is machine specific and not profile related.
Version of Office 365 installed: 1705 (Build 8201.2209).
We experienced this exact behavior in Outlook 2016, the solution was to enable protected mode for the restricted and internet zones.
The easiest way to change this is in IE.
In Internet Explorer, click the Tools button, and then click Internet Options.
Click the Security tab, and then select the Restricted Sites Zone.
Select the Enable Protected Mode check box, and then click OK.
Restart Internet Explorer.
Here is a little more information:
https://support.microsoft.com/en-us/help/2761180/apps-for-office-don-t-start-if-you-disable-protected-mode-for-the-rest
Try this:
1) Close Outlook
2) Rename the folder C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook
to C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook.OLD
(Where %USERNAME% is current User Name.)
3) Start Outlook, Setup User Profile
4) Add/Test Add-In.
If that works, then something broken on old Outlook profile. But if same problem: Exit Outlook, delete the Outlook folder and rename Outlook.OLD back to Outlook.
I ran into this exact same problem after uninstalling Visual Studio 2015 on my development machine. (I had been using Visual Studio 2017 for Outlook add-in development.)
The problem went away as soon as I reinstalled Visual Studio 2017. The Outlook 2016 installation had nothing to do with the problem, I never changed Outlook or its profile at all.
This would indicate that the problem is somehow related to the SDK tooling on the machine...perhaps something to do with the .Net framework?
If I ran into this problem on a customer machine I would try reinstalling or repairing the .Net framework, or perhaps reinstalling Outlook (assuming it contains some add-in tooling that is broken.)
Just passing this on in case it helps anyone else.