Issue Excel library, what am I missing? ".CurrentWorkbook.FullName" not a member of UiPath.Excel.WorkbookApplication

The bot was developed in UiPath version 2016.2 and after upgrading to 2018.1.4 it has validation errors as pictured.
What am I missing?


please try dir(path)

Thanks, but the issue is not with the path syntax, is getting excel file name (full name/path) from the currently opened excel:
“CurrentWorkbook” is not a member of UiPath.Excel.WorkbookApplication which worked perfectly fine before upgrading.

have you imported Microsoft.Office.Interop.Excel .?

yes, everything is imported

I have uninstalled UiPath.Excel.Activities, closed UiPath and then re-opened, it seems to work and fixed the issue :slight_smile:

It seems that the latest version of UiPath.Excel.Activities package 2.4.6856.17931 is causing the issue, reverting back to the previous version 2.3.6682.26635 solved the issue.

Hi @Alinutza13

Could you maybe check as well with the newest package:

It was released yesterday.

same issue with the version released yesterday, version 2.3.6682.26635 still works fine.

Thank you. We will try to get to the bottom of it.

Could you recreate the issue for us? Please create a blank project with a sequence that uses only the problematic activities.

We will investigate :slight_smile:

Hello @Alinutza13

Thank you for this post.

We are continuously learning what is a good compromise between flexibility and robustness. Give the user too much freedom - some might lack responsibility and end-up in production with workflows that are impossible to maintain while keeping backward compatibility. Make things too tight - not much automation can be done.

The reason for your problem is I’ve switched the access modifier of the CurrentWorkbook field on the WorkbookApplication class from public to private. It wasn’t designed to be used in code like you did. There must be a more robust way of knowing the path to the currently opened Excel file, at the workflow level.

However, this scenario raises some interesting questions. We will open an issue and discuss it for the 18.4 release. It would be most helpful if you provided some background context of your use case. For instance:

  • where and for how long has this workflow been running
  • the XAML workflow itself (stripped of any confidential data); just to learn how people design workflows
  • how did you come to notice the problem
  • any other data that you consider relevant for our understanding our customers

Thank you in advance,