Unable to publish the workflow in alteryx gallery

[IC_Alteryx]

I am facing an error while publishing the workflow to the alteryx gallery as :• Tool #227: Cannot access file: D:\ProgramData\Alteryx\Service\Staging\37524_c615f597a0e54a5388658703d8bf3928\__StageTemp\Engine_43832_61fbcdb3588e477582126031b5d65646~\rdml_budget_data Extract.hyper (ToolId: 26) . 

My input is a tableau hyper extract file and we are connecting through our organization shared drive . 

Can anyone help me with this issue

[abacon]

@IC_Alteryx If the Hyper file is on the shared drive, you will want to do 2 things:

1. Under options>advanced options>manage workflow dependencies and click the tableau output tool, hit the UNC option. This changes the file path to the fully name so the server can hit it.
2. When you publish the workflow, before you hit save, click manage workflow assets, and uncheck the file path for the Hyper. This will keep the file path as you set it when you push it up and not change it to a spot on the server.

When you push up files to the server, they get saved to a location on the server unless you uncheck it under manage workflow assets. Once you do that, it allows the workflow to look for the file as you have set the path. If this doesn’t work, make sure your server can hit the shared drive then do the above again.

if this works for you, please mark it as the solution so others may find it.

abacon

[Ryan247Zook]

Hello!

The error "Cannot access file: D:\ProgramData\Alteryx\Service\Staging...\rdml_budget_data Extract.hyper" when publishing to Alteryx Gallery indicates a file access permission issue on the Gallery server. The most common cause is that the Alteryx Server service account lacks sufficient read/write permissions to the staging directory (D:\ProgramData\Alteryx\Service\) or, if your Tableau Hyper file is on a shared drive, it might also lack network permissions to access that original source during workflow packaging. Your Alteryx administrator or IT team will need to verify and adjust CatTranslator Org these server-side file and network permissions for the Alteryx service account to resolve the problem.