1

I've created a workflow in Automator that isn't working as expected.

I started with an 'ask for text' action and a 'set value of variable' action (ProductCode). Then a 'New folder' action using that variable as part of the name and that works fine giving me (ProductCode)_Master Folder.

The trouble I'm having is using the variable again, when I use the (ProductCode) variable to name another folder, I'm just getting $(6BF6D2D6-19E6-474A-99CC-78F5F7F8E44F) instead of the (ProductCode).

Here's a screen grab of the workflow with results. Any help would be appreciated.

Workflow screen grab

13
  • Now that is weird—so the variable returns something totally different the second time you use it, even though you don't set it between those two uses. This might be an Automator bug. (A really bad one!) May 28 at 16:14
  • ...what happens if you save the second folder in a different location? I wonder if it's doing this because you can't have two folders in the same location with the same name? May 28 at 16:15
  • Still the same thing unfortunately :( May 28 at 16:16
  • If you wanted to post the Workflow somewhere, I'm curious to see what will happen if I run it in my much older version of Automator. May 28 at 16:18
  • @Wowfunhappy, RE: "I wonder if it's doing this because you can't have two folders in the same location with the same name?" -- The Automator workflow pictured in the OP is not attempting to create two folders with the same name. It is clearly attempting to create two folders with different names. One called [ProductCode]_Main Folder and the other [ProductCode]_New Folder. May 28 at 16:22
0

I realised why the variable wasn't working when using it a second time. There was a space at the start of the folders name.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .