We put together a new manifest with two VersionOverrides sections, the outer one requiring Mailbox Set 1.4, and the inner one requiring 1.5. Our app shows up in OWA, and Outlook 2013, but does not show up in Outlook 2016 and Outlook 2019. The validate-office-addin tool doesn't detect any problem with the manifest. On the Outlook 2019 client we set up 'run time logging' as described here: https://learn.microsoft.com/en-us/office/dev/add-ins/testing/troubleshoot-manifest to see if it would log any 'installation' issues. The file was created but the file size is 0. The back-end is Exchange Server 2016. If we go back to the earlier manifest we had, the app shows up again. Is there a way to determine what is wrong with the manifest (or with Outlook)?
The Outlook web add-in didn't show up in Outlook 2016 or Outlook 2019 because there was a duplicate resource string in the manifest file. In my case, the duplicate looked like this (the 'DefaultValue' is not relevant):
<bt:String id="paneReadSuperTipDescription" DefaultValue="misc text"/>
<bt:String id="paneReadSuperTipDescription" DefaultValue="more misc text"/>
Related
I have tested my add in Outlook Web access but to complete the testing I need to sideload my add in to the Outlook 2016 client.
The only information I can find on this is located here and is out of date as I cannot get to the store from my latest version of Outlook
https://learn.microsoft.com/en-us/outlook/add-ins/sideload-outlook-add-ins-for-testing
Please can someone help me find some up to date documentation on this or just explain how I can load the add-in into Outlook 2016?
This documentation is current.
On the Home tab in Outlook 2016, select 'Get Add-ins'.
On the next screen select 'My add-ins' on the left hand side
Scroll down to 'Custom add-ins'
Click on 'Add a custom add-in'
I use MS Office 2013 and Windows 7 in a networked environment.
I have an auto-open Excel VBA program that sends files via Outlook and is scheduled via Task Scheduler.
This ran when I was on MS Office 2010, but my computer was wiped and reinstalled with MS 2013.
Some key points:
The Excel files all work when I run them directly and the emails get sent via Outlook.
Task Scheduler works when I use the setting "Run only when user is logged on" and emails get sent via Outlook.
Task Scheduler works with the other parts of the Excel VBA when it runs as "Run whether user is logged on or not," but does not successfully send Outlook files. I know this because I included a line to save a file in a particular directory and it did save it there. I also saw Excel in the Task Manager processes. So it runs, but does not send the Outlook email.
Things I have tried already:
Changed DCOM settings for Microsoft Excel and Outlook Message Attachment
Created "C:\Windows\System32\config\systemprofile\Desktop" and "C:\Windows\SysWOW64\config\systemprofile\Desktop" directories
Using the Outlook Object Model in a Task Scheduler or in the context of a Windows Service is not supported, so this could explain some of the unexpected behaviour. See: https://support.microsoft.com/en-ca/help/237913/the-outlook-object-model-is-unsuitable-to-run-in-a-windows-service
When submitting our addIn we got the following message back:
If you do not support 2013 SP1 because you are using an API only available in 2016/Online, you must put these apis in the requirements tag in your manifest.
Our addIn does not work in Office 2013 since it uses both WordApi and ExcelApi (When opened in Word and Excel accordingly) which is not available in Office 2013.
Therefore we tried to specify in our manifest file that our addIn requires WordApi 1.1 by adding this to the manifest file:
<Requirements>
<Sets DefaultMinVersion="1.1">
<Set Name="WordApi" MinVersion="1.1"/>
</Sets>
</Requirements>
However, when we add the requirement of WordApi then the addIn doesn't show up in PowerPoint and Excel and vice versa.
How do we specify that the addIn is not available in Office 2013 without having to create separate manifest files for each office Host?
If your manifest contains Word API (or any host specific API) then it will not show up in other clients.
If your add-in is designed to work in multiple clients, and requires an API not currently supported in Office 2013, please include these details in the test notes of your next submission. Should the validation team need any additional information to resolve the issue, they will reachout to you at the email address on record to discuss how to proceed.
It looks like you're tag is correct. I don't have a solution but perhaps something to try. I've read that the location of the Requirements Tag matters. I put my requirements tag above the tag.
The article [https://learn.microsoft.com/en-us/office/dev/add-ins/testing/troubleshoot-manifest][1] discusses validating your xml file with office-toolbox. You run the command "npx office-toolbox validate -m MANIFEST_FILE" (see the article for full details). When I run this validation command on my manifest which has ...
<Sets DefaultMinVersion="1.1">
<Set Name="ExcelApi" MinVersion="1.1"/>
</Sets>
</Requirements>```
It returns
```Validation: Passed
Based on the requirements specified in your manifest, your add-in can run on the following platforms; your add-in will be tested on these platforms when you submit it to the Office Store:
- Excel for iPad
- Excel 2016 for Mac
- Excel 2016 or later
- Excel Online```
The key here being that it recognizes that it is only valid for Excel 2016. We've been using this to identify when our tags are working without having to submit to MSFT.
[1]: https://learn.microsoft.com/en-us/office/dev/add-ins/testing/troubleshoot-manifest
Following this thread, I have modified the manifest file of my two add-ins, and resubmitted to the store. Yesterday, I got a mail to say one is approved, and today I got another mail to say the other one is approved as well.
However, I could not find them in Excel 2016 for Windows. Then I go to the web page of the Office Store. I could find the two add-ins, but I see in their page: This add-in requires one of the following applications: Excel 2016 for Mac, that's it, it does NOT mention Excel 2016 for Windows. (I have not checked them in Excel 2016 for Mac, because I have not installed Excel 2016 for Mac).
The follows is the part related to version in their manifest file. So does anyone know how to modify this to make the add-in available in Excel 2016 for Windows, where my add-ins work fine.
Moreover, once I modify their manifest, I should unpublish the add-ins, and then re-submit them?
<?xml version="1.0" encoding="UTF-8"?>
<Hosts>
<Host Name="Workbook" />
</Hosts>
<Requirements>
<Sets>
<Set Name="ExcelApi" MinVersion="1.2"/>
</Sets>
</Requirements>
<DefaultSettings>
<SourceLocation DefaultValue="...Home.html" />
</DefaultSettings>
<Permissions>ReadWriteDocument</Permissions>
Your manifest is correct for enabling an add-in in Excel 2016 for Windows, Mac, and Excel Online.
It's possible that the validation team manually tagged your add-in to not support Excel 2016 for one of the following reasons:
You specified in the description or the "Testing Notes" field that the add-in shouldn't be supported on Excel 2016 for Windows.
The validators found a bug that was specific to Windows. Normally if that happened they would reject your submission at least once first and include an explanation in the report. So check all your previous submission reports for information.
If none of the above are the reason, then there was some other problem during validation, perhaps a bug. On your Seller Dashboard page:
Scroll to the bottom and click Support:
Problem type: App submission and validation
Category: App validation results
Start email (the team with expertise here is in Europe, so the chat/call is likely to be unsuccessful during North American business hours)
Describe the issue briefly/politely, including links to your add-ins, and submit
I have an isolated issue with a user who has IE 11, office 2013 and is trying to open office files stored on SharePoint 2010 document libraries.
When he clicks on the document, the office application starts but does not open the document. He has to download a copy of the document and make changes locally.
Other users can open the files fine and their client instance of the office application works no problem to open the document. This behaviour is the same for any office file on the SharePoint 2010 farm. pdf files behave normally and open in acrobat. With text files notepad doesn't even appear so slightly different but still incorrect behaviour.
I have tried adding the site to his trusted sites in IE. Using Firefox and the behaviour is the same. Repaired office, same issue. All other users are OK.
Any help appreciated as I have exhausted google.