snuziale / vsts-open-in-excel Goto Github PK

The Library you call VSS. was changed see: https://developer.microsoft.com/en-us/azure-devops/develop/extensions

It is not working after install. Popup window saying download TFS office integration, wich I installed and still not working.

VS403191: Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.ApplicationClass' to interface type 'Microsoft.Office.Interop.Excel._Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID ..........

I have TFS online and Visual studio 2017

The versions and even product (Team Foundation plug-in) are confusing in a number of ways:

• Seem outdated (specify 2017, when it's 2019)
• The link to "Visual Studio Office" plugin (the 2nd one) also brings me to the same page as the first one and I have to scroll it down a lot to find it (that's why I though initially that this was non-existent).

In short, there is less connection between the dialog and the page it links to that makes me feel as a user that something is wrong, compared to the 2 links getting me to the specific things to download or in another way have a tighter connection between the dialog and resulting page.

I'm using dev.azure.com using my work email,
Due to business policy, I need to change the password,
After password changed, when I open the query in Excel, it says

TF30063: You are not authorized to access 
https://dev.azure.com/{my-organization}

I've check google, stackoveflow, after some tries (empty %LOCALAPPDATA%\.IdentityService, empty %LOCALAPPDATA%\Microsoft\Team Foundation\8.0\Cache, delete Credentials in Control Panel... ), I've connect successfully to Azure DevOps in Visual Studio 2022 but still can not open query in Excel.

Is there any idea to fix this?

Steps to reproduce

WI has two fields eg "Country" and "Region".

Default value for Region "Global"
The "Region" will be filled also by some rules:
IF Country == "DE" THEN Region = "EMEA"
IF Country == "US" THEN Region = "Americas"
...

When opening now a query in excel which includes both fields and new WIs are created, then the "Region" first gets the default value. After publishing I can see the correct value for "Region" in Excel but not in AzDO

Press again to "Publish" doesn´t work, because the data "didn`t" change
When I edit afterwards another field, then the "Region" field will be updated correctly in AzDO

Running ADO 2022 on-premise and have the Open in Excel extension installed. When clicking on "Open in Excel" from the "Action" menu of a work item. It got a 403 error.

It also have the same issue when pull the workitems from the Excel application as well.

Hi Team,

I have installed "Azure Devops Open in Excel" extension, to import Work item into an excel sheet.

To have the extension work, I have to install "Microsoft visual studio 2019", which is also done.

I navigate to a query, click on "Open in Excel"

It opens excel sheet, but throws an error - "TF30063: You are not authorized to access http://dfcbi.visualstudio.com
Open In Excel Issue.pdf

I used the Azure DevOps Open in Excel integration to create the Test Suite Work items that now cannot be deleted. I think this is a bug.

Steps:

1. Create a Work Item Query
2. Add a new line with the Work Item Type “Test Suite”
3. Publish

User is attempting to pull work items with the Description field into excel. When the information is exported, however, some words are not spaced out properly, requiring rework to the excel values.

Hello,

Recently our users have observed that the 'Open in Excel' option that appears on the Query Results menu bar.

Error: VS403191: There was an error attempting to open work item(s) in Excel: TF80012: The document cannot be opened because there is a problem with the installation of the Microsoft Visual Studio Azure DevOps Office Integration components. For more information, see the following page on the Microsoft website: ....................................

On the 'Q & A' tab of the Extension page in the Azure DevOps Marketplace, a user states the following

"With ADO stopping TLS 1.0 and 1.1 connections, there was a warning running the open in excel function that it was not using TLS 1.2. Is this something that anyone is working on?"

The timing of when the users began to observe this problem does overlap with the TLS change(s). Please confirm whether someone is looking into this issue. I have noticed that is has been 5+ years since a commit was made to the repo. Thank you.

When I click on the New List icon in the Teams ribbon in Excel, I am unable to connect to the Azure DevOps Server.
Below is the error message that I received:
TF31003: Either you have not entered the necessary credentials or your user account does not have permission to connect to Azure DevOps server at https://dev.azure.com/********* Ask your server administrator to add the appropriate permissions to your account.
The following error was encountered TF30063: You are not authorized to access https://dev.azure.com/*********

This problem only occurs on one specific machine and works fine on other machines. The problem started occurring after I changed my password. My server administrator confirmed that I do have permissions to connect. On the same machine where the problem is occurring I am able to successfully connect to the same DevOps instance in Edge browser, Chrome browser, Visual Studio 2019 and Visual Studio 2022. So, this does not appear to be a permissions issue. We believe the problem might be due to invalid cached credentials somewhere.

Things that I tried but did not work:

• Cleared out all data from Edge, Chrome and IE browsers.
• Cleared out all cached windows credentials in control panel's credential manager.
• Deleted all files in my %localappdata%\temp folder.
• Uninstalled and re-installed the Azure DevOps integration.
• Repaired Office.

Any other ideas or suggestions?
Is there a registry key-value or cache file somewhere that I can try deleting?

Thanks!
Gregory

Hi,
We use TFS 2017.3, recently I update my office to Office 365 and now the extension doesn't work, there is a way to use the extension with office 365 in TFS on premise?
Thank you.

When I export a query with the column "Changed By" the first entry will be changed to changed by the person how export the results in excel, even when this person had never ever touched the WI

It can be easily reproduced onPremise with AzDo2020.1.1 and in Services as well.
I´m using

• Extension version 0.1.71
• VS2019 (16.11.8)
• Microsoft® Excel® for Microsoft 365 MSO (Version 2109 Build 16.0.14430.20154) 32-bit

It makes no difference which browser I´m using (tested with edge, chrome and firefox)

Hello!

I am unable to open the results of the query results in Excel. I have both Excel and the TFS Office Integration 2019 clients installed. Please see attachment for screenshot of the error message.

Note: I used to be able to do this until I uninstall and reinstall D365 Office on my machine.

Appreciate any guidance! Thanks!

Van
Cannot Open in Excel DevOps query.docx

Looks like this repo is out of date and what's published on the app store is from kunalranglani's fork. It'd be nice to get that PR accepted since this is where the link on the Marketplace comes from. We're looking to update the text on the dialog box and might be interested in submitting that as a PR too.

When trying to export a query result which uses the filter [Iteration Path = @CurrentIteration] the following error is shown in Excel

VS402612: The macro '@CurrentIteration' is not supported without a team context.

I installed the 2015 Office Integration 3.1 and that works great I can pull a query from there no problems. However, when on the VSTS web page and I click the Open in Excel button I get this error:

Error

TF400051: Cannot process URL tfs://ExcelRequirements/OpenQuery?cn=https://xxxxxxxxxx.visualstudio.com/DefaultCollection/&proj=xxxxxxxxxxxxxx&qid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx because it contains an unrecognized subsystem: 'excelrequirements'.

OK

I've tried Chrome and IE and both give the same error.

My Excel is part of Office 2016 Professional Plus (x64).

Any help would be greatly appreciated.

Hi,

We have TFS 2018 on-prem and i have installed VS 2017 and Team Foundation Server Office® Integration 2017.
Even after this it's asking for download again.

Thanks,
Raj

I adore this extension but now I am very sad as it has stopped working. See the following screen shots. The last picture gives you the version of Excel I'm running.

Hi,

Before we can implement this extension our security team would like answers to the following:

1. Is this extension being patched – i.e. kept up to date?
2. Who actually owns them?
3. Macros – does it run macros in the background?

Could anyone help or point me in the direction of someone who can.
Thanks

Not able to use excel in Azure DevOps

url: https://dev.azure.com/FedEx-IT-Can/

Open in excel errors out when opening queries in excel that has "Is Not Empty" as an operator
error message "Expecting comparison operator. The error is caused by <>."

Hi I am trying to use Azure DevOps Open in Excel. I go to my Azure DevOps environment and when I go to my queries and try to click more options and open in Excel I just get the error "The Macro @recentProjectActivity is not defined" but this only seems to happen when selecting more than two items. If I just select one item it will open in excel. I do not see a section for recent project activity in the item on Azure Dev Ops. I also made sure I have the Azure DevOps Office® Integration 2019 installed.

Hi,

I'm trying to open a query from ADO in excel, however, I'm getting the error TF80070.
I already installed the extension "Azure DevOps Office® Integration 2019". The tab TEAMS appears in my excel that indicates the extension was installed successfully.
If I try to open the project directly in the tab TEAMS on excel I got the same error message TF80070.

Team Foundation Server Office® Integration 2017 not support mac so I can't get the file

OK I had to cyberstalk you to figure this out, but I guess you used to work at MS, but don't anymore so this plug-in (and the Split) are no longer going to be maintained.
Could they be transfered to the Microsoft or ALM-Rangers organizations to be maintained going forward?

// random cc to @cschleiden since he seems to be on the VSTS extension group

Hi

We have enabled the extension, but while waiting to open it up, we see a dialog saying the user has to install the VS 2017 and onwards versions.
Then it takes about 10s to open excel.

I wonder if there is a way to speed things up?
Best regards,

Our users need to export Test Steps from VSTS, work on them in Excel and then publish the changes (including changes to Test Steps and Outcome etc) back to VSTS.

Is there any way to do this? I have found that exporting multiple steps for a Test Cast results in the steps being formatted as HTML in one cell in Excel. Any changes to this results in the Steps being reformatted as "normal" text and if that is then published back to VSTS, the test steps are completely lost. They are still visible in Excel but not in VSTS.

Is there any way that this can be achieved with the current functionality?

Hello,
First and foremost, thank you for this extension, our organization uses it frequently.
However, when opening any query that uses links other than Parent Child, the query result is flattened.
Example: Running a query for work items and their direct links, specifically Predecessor links. When opening the query in Excel, the file is flattened and it is impossible to tell which item is the predecessor.

Hi,

If I create query "Query across projects" and export the results to excel, only work items of the current project (where I run the query) are exported.

I got this message:

Can you fix it?

Thank you!

VSTS Open in Excel used to work with no issues, starting this week, a few members on my team including myself are experiencing an error when using the add in. Please see screenshot with error messages.

We have attempted to reinstall the TFS Office Integration 2017 but we still get the same error after reinstalling.

Our users have requested that I add the “Open in Excel” Extension to our VSTS Account. We have a requirement to review EULA’s before we approve software for usage within the organization. I need a copy to send to our Software Licensing team. Please send me a link to the EULA for this Extension so I can begin the approval process.

It worked flawlessly for exactly 2 days. After that, I'm not sure if coincidence or not, I changed my password and it stopped working. After some time, I were able to make it work again, but now I have to re enable it every time I open Excel and even after reenabling it, it isn't recognising tables created by it, probably because it's disabled on startup

I tried a few things:

• Registry (couldn't find the entries mentioned in the articles I found)
• Adding the Add-in location to the trust center thingy
• Reinstalling
• Adding the whole default Add-in folder to the trusted thingy
• Change Office Group Policies (I couldn't find the path to the setting I need to change mentioned in the article I found. Office isn't listed)

I really don't know what else I could be missing. I know my password can't be the issue anymore, because it now works properly when I reenable it

I was using this feature regularly with no problems. It stopped working within the last month. I keep getting this error. We have done some troubleshooting and support opened a case with Microsoft Support (TrackingID#2308170010012282). I was told to submit here.

VS403191: There was an error attempting to open work items(s) in Excel: Unable to cast COM object of type...

I would attach an image but don't see a way to. Please help.

Example