To resolve this issue, you should ensure that you provide the full and correct file path when working with Excel files.
Here’s how you can correct this issue:
Ensure Variable Contains a Full File Path:
Double-check that the thisFile variable indeed contains the full and correct file path, including the drive letter (e.g., “D:\systems\excelFiles\fileName.xlsx”).
Use the Variable Directly:
When using the Excel activities, pass the thisFile variable directly as the Excel file path without attempting to combine it with any project folder paths.
For example, in the “Excel Application Scope” activity, set the “WorkbookPath” property to thisFile.
Avoid Concatenating Paths Manually:
Ensure that you’re not manually concatenating paths in your workflow using string operations like “+” or "". It’s best to use variables that hold the full path to avoid path-related issues.
Verify File Existence:
Before using the Excel file, you may also want to add a check to ensure that the file actually exists at the provided path. You can use the “File Exists” activity for this purpose.
I was not able to fix the problem with the excel activity, but I was able to save the file to a static folder, and then use the move file activity to move it to the path variable.