Action tools not updating Output tool with this setting

[Smiller100]

Recently discovered something about how Interface tools work with the Output tool (after several hours of trial and error 🙂 ). In trying to update the file path for an Output tool using a File Browse tool, I found that neither the file path nor the name of the file would update to the specified options if the "Take File/Table Name from Field" box was checked in the Output tool configuration window. The same was true after attempting to use different Interface tools to achieve the same results, none of them were able to update the file path as long as that box was checked. Not sure if this is intentional or not, but it certainly seems that the file path should not be affected by an option surrounding the name of a file. If it is intentional and there is a way around it that I was not seeing, let me know! Just wanted others that may experience a similar situation to be aware of what my issue was and a potential fix.

[mbarone]

Can you post some screenshots of the configurations for your output tool and the action tool?

[apathetichell]

Could you post a screen grab of your action tool?

[Smiller100]

As soon as I unchecked that box, the file path was able to update to whatever path was specified by the user, but if it was left checked then it would revert back to the default file path that was set up in the Output tool.

[mceleavey]

@Smiller100 ,

But you can achieve the same by attaching the action tool to the formula tool that creates the output field you are using when you check the box.

Either is fine.

M.

[Smiller100]

Do I need a formula tool to specify the output field? Shouldn't I just be able to do it manually in the configuration window of the output tool?

[DawnDuong]

hi @Smiller100 

The file name is set to changed based on the input column "File" which has nothing to do with the Interface input (the file is #1).

I'm not entirely what's the expected outcome to be honest... would you be able to elaborate more the expected outcome that you want to achieve?
Dawn.

[mceleavey]

@Smiller100 ,

I think you're confusing yourself.

In the top window of the output is the hardcoded value:

You can either keep the config as it is and attached the action tool to the output and overwrite the value in yellow, OR:

You can configure as above.

This method is usually used when you are determining the filepath in a formula to make it dynamic. This means the formula tool that creates the "Filepath" field would look something like "C:\Users\Name\Documents\Test_"+datetimetoday()+"|||Sheet1"

This would make the filename File_2021-06-17.xlsx

If you wanted to overwrite elements of the filename dynamically in this method you would attached the action tool to the formula tool and overwrite the bits you want.

If you are just wanting them to select the filepath, then the first method gives you what you want.

M.

[apathetichell]

@Smiller100Here's the problem. The box you are checking allows for multiple files to be output from 1 output data tool. Your file browse tool accepts 1 location for a new file. That's a potential conflict. Output data has a parameter called "Multifile" this is set to "True" when that box is clicked. Otherwise it is set to "false." If it is set to "True" then file browse isn't going to work because that isn't providing you multiple potential locations.

If you were making a dynamic workflow with optionality  to allow a user to go for multifiles or use a filebrowse tool - you can update the the specific True/False multifle option with a second action tool set to formula - pointing to the correct location.

[Smiller100]

Yes Dawn,

I'm not trying to change the file name with this interface, just trying to allow the user to choose the file path for where they want the output file to be saved. This workflow was passed off to me by a colleague who told me I was to build an app that allowed a user to input files and choose where they wanted the output file to be sent to, and for some reason the only time where the app actually sent the output file to the correctly specified path was when this box was unchecked. Maybe some other setting somewhere else in the workflow is to blame, I'm honestly not sure, but this was a quick fix that I found to work.