Invoke Workflow file - Directory change?

Hello Robot Overlords!

Having an issue i can’t seem to resolve and i’m hoping one of you can help sort please.

I have a Workflow (let’s call it MainFlow) that passes a few arguments to another workflow and expects some other arguments back. I’m using “Invoke Workflow File” activity.

Now other workflow is in a completely different directory, but when i invoke workflow i get error saying it can’t find file path, then list the file path as “Mainflow filepath \ other Workflow path”

I cant seem to remove the MainFlow path from the start of the other workflow path no matter what i try. i have set variable and used absolute path, no joy. i have tried the change the workflow directory and many other things, but i just cant remove Mainflow path from invoke path.

Invoke was working on older version, but am now using 2024 version and it hard codes MainFlow path into the invoke…how do i fix this?

Thanks

Hi @MikeBlades,

Seems like you are now working in windows based project and earlier were on windows-legacy project.

Refer below thread for more details:

Regards
Sonali

@MikeBlades,

Invoking workflow/xaml which is located outside of the project folder is no more supported.

All xaml should be in your project folder.

Move all the dependent workflows inside your project and refer same
You can create sub-folders to segregate but should be within the project folder

In the latest versions - Only relative reference will work even if the workflow is within your project folder. Hence - it is mandatory to keep all workflows within your project and do a relative reference

Hence it is coming as dropdown instead of folder selection

@MikeBlades

If the xaml you want to invoke is in a separate project then you need to use invoke process and not invoke workflow file

Invoke workflow supports only in same project

Create an entry point foe r the xaml you want to run and invoke that process

Or you need to copy the xaml into current project and then invoke workflow supports

Cheers