How to implement add-in which works both in Excel and Word and has specific API requirements

%3CLINGO-SUB%20id%3D%22lingo-sub-481282%22%20slang%3D%22en-US%22%3EHow%20to%20implement%20add-in%20which%20works%20both%20in%20Excel%20and%20Word%20and%20has%20specific%20API%20requirements%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481282%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20Excel-based%20add-in%20was%20recently%20upgraded%20to%20work%20with%20both%20Excel%20and%20Word.%20Initially%2C%20we%20created%20a%20separate%20add-in%20for%20Word%2C%20but%20our%20submission%20was%20rejected%20and%20we%20were%20asked%20to%20combine%20both%20submissions%20into%20a%20single%20one%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EThis%20add-in%20appears%20to%20be%20a%20duplicate%20of%20your%20Excel%20add-in%20already%20submitted%20to%20AppSource.%20Duplicate%20add-ins%20are%20not%20permitted%20on%20AppSource.%20Please%20combine%20support%20for%20all%20clients%20required%20in%20one%20add-in%20submission.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EWe%20did%20that%20but%20immediately%20faced%20another%20issue.%20Our%20add-in%20has%20a%20dependency%20on%20WordApi%201.3%20and%20ExcelApi%201.7.%20Unfortunately%2C%20there%20is%20no%20way%20to%20put%20both%20requirements%20together%20in%20the%20same%20add-in.%20It%20makes%20a%20list%20of%20supported%20hosts%20empty%20because%20none%20of%20them%20obviously%20support%20both%20APIs.%20So%20we%20made%20a%20submission%20without%20those%20requirements%20set%20in%20the%20manifest%20and%20made%20a%20comment%20about%20it%20in%20test%20notes.%20Unfortunately%2C%20our%20submission%20was%20rejected%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EYour%20add-in%20is%20not%20working%20in%20the%20following%3A%20%E2%80%A2%20Word%202013%20client%20on%20Windows%207%20%E2%80%A2%20Excel%202013%20client%20on%20Windows%207%20(Note%3A%20The%20add-in%20framework%20uses%20Internet%20Explorer%2011%20to%20run%20the%20add-in)%20If%20you%20do%20not%20support%202013%20SP1%20because%20you%20are%20using%20an%20API%20only%20available%20in%202016%2FOnline%2C%20you%20must%20put%20these%20apis%20in%20the%20requirements%20tag%20in%20your%20manifest.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EWe%20are%20in%20a%20deadlock%20now.%20It%20seems%20there%20is%20no%20way%20to%20meet%20those%20requirements.%20We%20sent%20an%20e-mail%20to%20Office%20Validation%20Team%20asking%20for%20clarification%2C%20but%20haven't%20heard%20back%20from%20them%20yet.%3C%2FP%3E%3CP%3EHow%20do%20we%20specify%20that%20the%20add-in%20works%20in%20Office%202016%20(Windows%2FMac)%20and%20Office%20365%2C%20but%20not%20available%20in%20Office%202013%3F%20Our%20App%20ID%20is%2042949677685.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-858416%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20implement%20add-in%20which%20works%20both%20in%20Excel%20and%20Word%20and%20has%20specific%20API%20requirements%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858416%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F410161%22%20target%3D%22_blank%22%3E%40TriSys%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-858409%22%20slang%3D%22en-US%22%3ERe%3A%20How%20to%20implement%20add-in%20which%20works%20both%20in%20Excel%20and%20Word%20and%20has%20specific%20API%20requirements%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-858409%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20Outlook%20add-in%20was%20also%20rejected%20with%20these%20messages%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYour%20add-in%20is%20not%20working%20in%20the%20Outlook%202013%20client%20on%20Windows%207%20(Note%3A%20The%20add-in%20framework%20uses%20Internet%20Explorer%2011%20to%20run%20the%20add-in)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20do%20not%20support%202013%20SP1%20because%20you%20are%20using%20an%20API%20only%20available%20in%202016%2FOnline%2C%20you%20must%20put%20these%20apis%20in%20the%20requirements%20tag%20in%20your%20manifest.%20If%20you%20are%20not%20using%20an%20API%20only%20available%20in%202016%2FOnline%2C%20then%20you%20must%20support%202013%20SP1.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20there%20is%20no%20information%20anywhere%20about%20exactly%20what%20I%20should%20put%20in%20the%20manifest.%20Why%20do%20they%20simply%20not%20state%20precisely%20what%20changes%20I%20need%20to%20make%20to%20my%20manifest%20rather%20than%20rejecting%20it%20and%20forcing%20me%20to%20do%20yet%20more%20research%2C%20spending%20valuable%20time%20and%20money%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F132064i30781F300B664FF4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22microsoft-seller-dashboard-rejection.png%22%20title%3D%22microsoft-seller-dashboard-rejection.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Our Excel-based add-in was recently upgraded to work with both Excel and Word. Initially, we created a separate add-in for Word, but our submission was rejected and we were asked to combine both submissions into a single one:

This add-in appears to be a duplicate of your Excel add-in already submitted to AppSource. Duplicate add-ins are not permitted on AppSource. Please combine support for all clients required in one add-in submission.

We did that but immediately faced another issue. Our add-in has a dependency on WordApi 1.3 and ExcelApi 1.7. Unfortunately, there is no way to put both requirements together in the same add-in. It makes a list of supported hosts empty because none of them obviously support both APIs. So we made a submission without those requirements set in the manifest and made a comment about it in test notes. Unfortunately, our submission was rejected:

Your add-in is not working in the following: • Word 2013 client on Windows 7 • Excel 2013 client on Windows 7 (Note: The add-in framework uses Internet Explorer 11 to run the add-in) 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.

We are in a deadlock now. It seems there is no way to meet those requirements. We sent an e-mail to Office Validation Team asking for clarification, but haven't heard back from them yet.

How do we specify that the add-in works in Office 2016 (Windows/Mac) and Office 365, but not available in Office 2013? Our App ID is 42949677685.

1 Reply

My Outlook add-in was also rejected with these messages:

 

Your add-in is not working in the Outlook 2013 client on Windows 7 (Note: The add-in framework uses Internet Explorer 11 to run the add-in)

 

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. If you are not using an API only available in 2016/Online, then you must support 2013 SP1.

 

But there is no information anywhere about exactly what I should put in the manifest. Why do they simply not state precisely what changes I need to make to my manifest rather than rejecting it and forcing me to do yet more research, spending valuable time and money?

 

microsoft-seller-dashboard-rejection.png