This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Hi @terrellchong, you can copy the result of one workflow and input it into the second.
1) Insert a browsing tool at the end of your workflow.Click on the button marked with red then copy all the records with header.
2) Insert a Text Input tool then paste all the records into it, by clicking the button circled with red.
In this way you can use the output of sheet hp as input of sheet hfm.
Other way is using an output tool and save the file as csv then put that file into the other workflow in case your data is dynamic and you are not willing to update your input file over and over again in hfm workflow sheet.
I do not believe you can transfer individual records by drag and drop-like actions the way you seem to be contemplating doing.
However it is not hard to transfer records between workflows. One way to solve your issue is to output the set of values of interest using an output tool and then use an input tool to import them into the other workflow. You will then need to join/union/append the records as appropriate in order to add them into the other workflow's data stream.
Will this transfer approach conserve the original meta-data encoding in the other workflow, or will he run into the usual potential problems with the text input tool (where integers are loaded as strings or bytes, etc.)?
@terrellchong, in case you are moving both the workflows as a single workflow then do not forget to use block until done tool on workflow no 2, where you will be using the the output file as the input file of worflow no 2 else you might face issues while running the workflows.
@grazitti_sapna I'm well aware that the tool does this under normal circumstances, that was why I asked; I was curious if it also behaved like that in this case. The point being that this behaviour by Alteryx can potentially cause problems if not addressed because the auto-detected data types may not match the data types the user had defined for his variables in the other flow prior to transfer, meaning variables don't behave the way he expected them to (joins not working, formulas not working as intended, etc.).