One Parameter for using in all the Formula Tool?

Hello,

Currently I have multiple formula tool used through different data sources in my workflow

But that formula tool has the same logic used applied.

It basically has the location to store the file.

The logic used in the formula: "C:\Users\abc\Desktop\folder\folder2\Output\"+[Group]+".xlsx|check"

I would expect "C:\Users\abc\Desktop\folder\folder2\Output\" part of the formula to be added dynamically by the user. The rest is constant.

I want to make the location of the file dynamic as when the user runs using the Analytics app. They should be able to enter the location of the file and then that text should be used in the formula tool.

How can I achieve that?

Thanks!

Workflow

Settings

Output

Help

Interface Tools

Accepted answers

DataNath

@madhurinani from the looks of it, you're replacing the entire formula expression. As you are using the File Browse tool to change the target directory, you only want the filepath part of the formula expression to be replaced and so you'll need to reduce the replacement argument down to that. Something like the following:

New Workflow5.yxwz

All comments

DataNath

Hey @madhurinani, as part of a macro I built a little while ago, I did exactly this. Whilst your use case is an application, the approach will be exactly the same - the File Browse tool updating a directory within a formula tool.

File Browse tool which prompts the user for their save location:

The starting/dummy filepath I used to first build the macro (the other one is the same):

The action tool is set to only replace the directory part of the formula expression:

Like in my macro, you can use a single interface tool and have it impact on multiple tools (in this case, formula tools) by connecting a separate action tool to each. I've attached my file for you to look at and reverse engineer - hope it helps.

Multiple Excel Outputs.yxmc

madhurinani

@DataNath : Somehow when I try to reverse engineer your workflow, I'm unable to recreate the scenario that I needed.

Below are the screenshots that I did when I replicated your workflow. But once I run as Analytic App,the location still goes to defaults even if I select something from the File Browse option.

Any idea where I could be going wrong?

madhurinani

@DataNath I am attaching my workflow for reference. Forgot to upload it last time.

@DataNath : Thank you for your feedback. It worked!

madhurinani

hello @DataNath :

I am facing an issue when I share this workflow with someone else.

When the other person open the workflow, it shows an error on the Output Data side which says that they cant access the folder path that is present on the Output data tool.

I understand that when I create the workflow, I put the local path that is present in my system. But when someone else opens the workflow in their system, it shows an error.

Do you have any idea how I can fix this issue?

DataNath

Hey @madhurinani, this is indeed because you have set the app up with your local directory that they don't have access to. However, when the other user runs the app, this will be replaced as expected by their selection and it won't actually error, it's just when you open it as the underlying workflow. You could try making the filepath relative https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/How-To-Use-Relative-Paths/ta-p/1160 or just explain to that it's not actually an issue.

madhurinani

@DataNath :

Agreed on your point and i also tried to use relative paths based on the link you had shared earlier.

To your comment: However, when the other user runs the app, this will be replaced as expected by their selection and it won't actually error.

This is where the issue is still coming. When the user runs the App, It allows to select the Folder using the browse condition.

But then once the user clicks on "Finish", it points an error to the Output Tool which has the file path of my local machine.

Thanks.

DataNath

Apologies @madhurinani I should've noticed this the other day, but I've just had another look at your app.

At point (A) of the workflow, you're asking the end user to select a folder to save the workflow to which is creating a custom filepath that then feeds into your Output Data tool. At point (B) in the workflow you're then asking them again to define a location and file name etc, even though you've already created this in the Formula tool before hand. Therefore, you only need one of these - either the Formula tool which overwrites the entire filepath, or the File Browse that acts upon the Output Data tool directly. If I run the workflow in debug mode and select a directory, you can see that this is replaced correctly in the Formula expression and so should work as the output tool is configured correctly:

If you're still having issues, can you perhaps upload the actual app you're having problems with if it's not the same one that I have?

madhurinani

@DataNath: I removed the File Browse tool and yet it does not work.
attaching the workflow.

I would say, run the workflow and choose your destination folder as required.

The file path in formula tool is not your local machine address and should work for my use case.

New Workflow5 (2).yxwz

DataNath

@madhurinani I just tried it and it didn't work. When looking at the setup, this is because in you current setup, you're looking for 'C:\Users\minani001\Desktop\Bayview Legacy run\BV legacy input\Output' as the replacement target within your action tool:

However, in your Formula expression you actually have 'C:\Users\abc\Desktop\Legacy run\BV legacy input\Output' and because they're different, Alteryx doesn't its target to replace and just leaves it as is. Therefore, you need to update your replacement target to the exact filepath that you're building out the workflow with, even if it's a dummy.

If I do that and open a debug workflow, the replacement works as desired:

madhurinani

Hello @DataNath :

To you comment:

"Therefore, you need to update your replacement target to the exact filepath that you're building out the workflow with, even if it's a dummy"

The file path cant be a dummy file path if you are using the exact file path, right?

Or maybe I am misinterpreting it .

Would you please be able to share the workflow that you edited on the debug part and I can run it on my machine and check if its working or not as expected?

That would really help me figure out what am I doing wrong.

Thanks

DataNath

@madhurinani whatever you put into your Formula expression that builds the filepath essentially just acts as a placeholder, as it'll always be replaced by the user's selection, and therefore it can be whatever you want it to be (hence why I said dummy, as it just doesn't matter). I've attached the amended app with the Action tool reconfigured. Can you check if it works now? Cheers

New Workflow5 (2) (1).yxwz

madhurinani

@DataNath : Its not working.

WHen I open the workflow. I see the below error. which basically says that they cant access the folder path

Now when I run using the analytics app.

I get the below error

Thanks.

DataNath

@madhurinani I think the issue may actually be caused by using a relative filepath in the 'Output Data' tool which we used to try and get rid of the previous error message (that's not actually an error at the time of running the app). If you make this absolute and then try running the app, does that help? I've just tried it and seemed to work for me.

madhurinani

@DataNath : So when I make it absolute and run the report, it works fine for me as the absolute path is on my machine.
But when someone else runs the report, it shows error for Output data

DataNath

@madhurinani if you reduce the filepath sitting in the Output Data tool down to something like this, does that work now?

.\Legacy.xlsx|||Original

Was having the same issue as you but this seems to solve it as the one in there currently is relative, but relative to the rest of the path you had afterwards which other users may not have.

Quick Links

This months top contributors

FláviaB 262

caltang 177

DanM 167

IraWatt 157

gawa 157