Problem with setting a dynamic file path to a one drive connector

I have a problem with setting a dynamic file path to a one drive connector.

I use the read range activity with a path to a file that lies on a one drive folder. This path is dynamic because the filename chan change. So it has a variable inside it.

THe problem is now when i publish the process and add it on orchestrator im forced to use a path thats not dynamic anymore:

How can I fix this, or is this not possible?

Hi @ShadowDom

Try you need to store the filename (or part of the path) in a config or asset, then build the full path inside your workflow using variables.

@ShadowDom,

In your code make sure you are passing the file name through a variable. Republish the project. Now the Orchestrator won’t ask you for the file name.

Hi,

I’m already doing this:

@ShadowDom,

Try updating the Integration package to latest possible version. After that delete the existing activity and readd it. Republish and try.

Thx for helping me out. I already have the newest update installed. What was also weird was when I created the output variable for the read range it did the type as DataTable4 (instead of DataTable).

Any other ideas?

@ShadowDom,

That should be DataTable not sure about the reason. Try recreating the variable as well.

@ShadowDom
Just try to use an orches. asset or input argument for the filename. Build the full file path dynamically inside the workflow.
access oneDrive files via synced local folder path on the robot machine if possible. manually set output variable type to System.Data.DataTable if not…

@ShadowDom

so one thing you would observe is do not select the connector from process again..let it be as user selection and in process select the default one you need that way it would not change and use variables

cheers