Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Export Workflow Temp.yxdb is missing

stevenlsj789
8 - Asteroid

Hello I have the workflow attached below with only one attachment (input excel file). Somehow, when i try to export the workflow, it shows a list of input (clenase.yxmc and Select Records.yxmc) and missing input (temp.yxdb). 

 

So when i tried to open the exported workflow, there is error message attached below. Any idea how to fix it? Thank you!

 

4 REPLIES 4
CharlieS
17 - Castor
17 - Castor

The Data Cleansing and Select Records tools are actually macros installed with Alteryx Designer. If you right-click on those tools, you can open and view the macros in Designer.

 

When exporting a workflow, the dependencies of the workflow and all macros are noted for inclusion. The W:\temp\temp.yxdb was what the Alteryx employee who built the Select Records tool used as the input file while testing. These are not references that you set up or configured.

 

Long story short, these referenced are only found in the Macro Input tools of those macros that get replaced whenever the macro is actually used. You don't need to worry about including those files so leave it unchecked and export the workflow without worry.

stevenlsj789
8 - Asteroid

@CharlieS

Thank you for your help. That makes a lot of sense. My only concern with not doing anything about it is when i send this exported workflow to some external user and when they open it, it shows those error message in the file below, which doesn't inspire a lot of confidence and credibility. Is there a way for me to remove those error message? Thanks! 

CharlieS
17 - Castor
17 - Castor

Happy to help! 

 

You could open the Select Records tool, change that Macro input tool to the "Text Input" option (with a dummy field) and save it as a new macro (access to the original is generally denied). Then insert that saved macro and use it like the original tool.

BretCarr
10 - Fireball

I agree this is a bit on the sloppier side (development wise) and leaves a gaping potential-error sitting there. I just had issues with this tool and I wonder if the missing file was the culprit because it would just sit there in limbo forever until I killed it. I then deleted those tools and the workflow blazed past like nothing ever changed.

Labels