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
Related
we have excel js add with custom function support and because of it, this add-in works just in excel office 365 version.
here we met a problem - "npm validate" define this add-in as an add-in for excel 2016, but that is not correct for us.
so the question is - how to correctly set the "requirements" section in the manifest file to define this add-in as an add-in for office 365?
currently, it looks like
<Requirements>
<Sets DefaultMinVersion="1.1">
<Set Name="CustomFunctionsRuntime" MinVersion="1.1"/>
</Sets>
</Requirements>
Custom Functions use separate requirement sets from the core Excel JavaScript APIs. You could refer to this page for Custom Functions requirement sets:
Custom Functions requirement sets
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"/>
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
I'm trying out the new style JavaScript based office add-ins and can't see how I can add the add-in launcher button to the ribbon.
I know that Command add-ins which can add tabs etc are not released yet, I'm just talking about a button that will launch my add-in.
It's a TaskPaneApp.
It seems to be possible because (in my version of office 16 at least) I can see that under the Insert tab, Wikipedia add-in has it own button in the Add-In group.
Currently I've just added a Shared Drive as a trusted location and am launching the app from there. As this is an internal app, it's likely to stay there.
Thanks
You just need to add some elements to your manifest file:
https://msdn.microsoft.com/EN-US/library/office/mt621545.aspx
Make sure you are using the latest version of Word, Excel or PowerPoint; it must be 16 or higher.
Also, make sure to use HTTPS requests.
The XML manifest is super sensitive.
Look for closing /> for all the tags, because you might be missing them somewhere.
You could also use this NPM module which is supported by Microsoft to validate your XML file.
I had migrated a SharePoint 2010 web application to SharePoint 2013 and running in compatible mode.
i have a SharePoint designer modified master-page which is saved in content database. i had some inline codes running in master-page.
the master page was working fine in SharePoint 2010.
i had this line added in page parser
<PageParserPath VirtualPath="/_catalogs/masterpage/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" />
but in 2013 I still have the same line but it still gives me this error
An error occurred during the processing of /_catalogs/masterpage/custom.master. Code blocks are not allowed in this file.
when i change the entry in page parser to this it works fine
<PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" />
which is not a good way as it opens all my pages to allow scripting.
any idea what is the change in 2013 and what is the best way to achieve this in 2013
here's my code:
<PageParserPath VirtualPath="~/_catalogs/masterpage/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" />
And it works fine on my end.
i got it to work in 2013 by setting the virtualpath to "~/_catalogs/masterpage/*"
Did you modify the master page in SharePoint 2010, or only in 2013?
This page: http://blog.bullseyeconsulting.com/archive/2013/03/21/fixing-code-blocks-not-allowed.aspx
Quoting:
As soon as it is "customized" (formerly known as "unghosted"), the reference to [the master page] for that site is in the database, not the file system. Without a change to web.config, code blocks are not allowed and the page breaks.