I am trying to develop an extension that runs on a Windows machine and supports a commercial Office 2019 Excel. Excel uses IE11 perpetual browser for this. When trying to load the name using
workbook.load("name"); await context.sync();
It gives "The API you are trying to use could not be found. It may be available in a newer version of Excel" . On doing a console.log(), I get against that property.
Can anybody help on what is the recommended way to fetch workbook name in Excel add-in?
Related
I am trying to convert an old Excel add-in to a new VSTO version. The present add-in reads data from an open Internet Explorer browser.
Since I.E will no longer be supported shortly, I am looking for a solution with an advance developing technology. The above issue is a major point without which this solution ill not be applicable.
Any help with a sample snippet will help.
I Have an add-in that is working on Excel in chrome, excel in Edge, but doesn't work in excel desktop.
Any clues?
Thanks
In the article amitklein gave, it says:
Office will still use the EdgeHTML base for add-ins until a build of Office 365 that supports Chromium is installed on the computer. We expect these builds to ship in 2020. They will likely appear in the Insiders channel in the first half of the year.
I haven't found the Chromium based Office 365 in insider channel so I think the version for now is still EdgeHTML based and Excel uses Edge Legacy.
I want to submit an add-in only for Excel Online (no Excel for Mac, no Excel for Windows).
Could anyone tell me if it is possible and how to configure the manifest xml file?
The Office store requires that the add-in works for Mac, Windows and Online with optional iPad support. It is not possible to select only some of the required platform. The same code that works on one platform should also work on the other with the addition effort being in the testing area.
Excel addin which uses Excel API 1.2. Add-in loads fine in Excel 2016 for Windows and Excel online. Save the file from Excel online and open in Excel 2013, addin fails to load in Excel 2013 with following errors:
When loading the Addin published in Store:
APP ERROR We can't load this app because we could not connect to catalog
When sideloading the addin from trusted catalog:
This app could not be started. Close this dialog to ignore the problem or click restart to try again
I know that Excel 2013 does not support Excel API 1.2. Could you please confirm the recommended way to make sure the add-in loads in Excel 2013?
• Should we use runtime checks using isSetSupported method?
• In such cases, how to debug which line of code is failing in Excel 2013 client?
• Is there any logging that can be enabled to troubleshoot such issues in Excel client?
I tried debugging a default add-in created by VS 2015 which uses Excel 1.2 API in Excel 2013. I added the following requirements set to the Manifest:
<Requirements>
<Sets DefaultMinVersion="1.2">
<Set Name="ExcelApi" />
</Sets>
</Requirements>
The addin also fails to load in Excel (15.0.4849.1003) when debugging using VS 2015. It works fine in Excel 2016 client.
I think there are two separate issues here (though there's a good chance that they're related, and the platform is simply giving the wrong error string. If so, let's confirm, and then I can file a bug to have us fix this).
Excel 2013 does not support the "ExcelApi" requirement set, which is a 2016 addition of the host-specific APIs (same goes for "WordApi"). If you specify ExcelApi in the requirements section of the manifest, as you have above, this will always fail to load in Excel 2013 -- by design. Essentially, you're requesting an API set and marking it as "required" for something that Excel 2013 does not support -- so it has no choice but to refuse to run it.
This is where the runtime check (isSetSupported) comes in. Please see my answer at Neat ways to get environment (i.e. Office version) for more details.
I am not sure what you mean by "how to debug which line of code is failing" or troubleshooting techinques. Essentially, any call to an Office 2016 API (anything in the ExcelApi set) from 2013 will result in a runtime failure...
Hope this helps!
I have an access 2007 application that exports data to an excel sheet and then opens the file. One user has just upgraded Excel to 2016. When it tries to export the file, I get the 'Could Not Find Installable ISAM' error. The code is simple and works on every other computer at the location, but no one else has Excel newer than 2010.
I followed the advice in the Microsoft KB article about checking for and re-registering the ISAM file - it is there and it looks fine. I repaired the office instillation and that did nothing as well.
My gut says that there needs to be a newer version of instruction to export with - I am using acSpreadsheetTypeExcel12Xml which is for Excel 2010, but Access 2007 has nothing supported newer than that. I don't have a version of Excel 2016 to test it on, but I can get on his computer from time to time. Also, I don't want to have to upgrade to Access 2010 if at all possible.
Thanks!