Can't import an existing workspace to a new ETL tool in a toolbox in ArcGIS Pro 3.3.1

[MattHowe]

I'm trying to add an existing workspace created using data interoperability to a new atbx toolbox in ArcGIS Pro 3.3.1. but when I add it it doesn't seem to register and is instantly removed. Has anyone seen this before?

After clicking OK etc then looking back into the properties I see the below.

[RenatoSalvaleon3]

After you click Ok on the New ETL dialog do you see this "Running..." message pop up and when its done the Spatial ETL tool appears on the atbx?

I don't have a Pro 3.3 machine right now to confirm this test made on Pro 3.4 but once I found one I'll retest and share my result.

Can you tell me what the behaior is on a new FMW file?

[MattHowe]

Hi Renato, Yeah I see the same running window. When it finishes and I open up the tool again, I get what you see in the second image above. On a new fmw file I get the same behaviour.

[RenatoSalvaleon3]

Just to state the obvious, have you tried Opening ang Running the ETL tool from the GP pane? Did it run and does the messages in the Message tab show any results, similar to the below? Scroll down to look for the Start - Process ID tag.

[MattHowe]

After I select the existing workspace, then OK everything. I try and run the tool and there are no parameters. If I run it nonetheless, I see this. I then go into the properties and the workspace I selected isn't there and the 'Workspace' option on the left is underlined in red.

[RenatoSalvaleon3]

Thanks. 

This confirms that the fme.exe command executable does not have the required fmw file parameter configured with the ETL tool.  Please submit a support issue and refer to this question in your case specifying as well if its reproducible in new projects or new atbx. I'll keep an eye on it.

Is the FMW file created from a version different from the current Pro 3.3.1 you are using?  There may be validation checks on the DI version to display that thumbnail. Let me check with our dev.

[MattHowe]

Ok, if I create a new ETL tool, I can't point it to an existing workspace. I have to open it and copy and paste all readers, transformers, and writers, and startup and shutdown scripts and paste it to the new ETL tool I just created. Absolute madness! Or is this normal? (Asking for a friend)

[RenatoSalvaleon3]

I did not ask you to create a new tool. I'm suggesting to open and run the "faulty" ETL tool and determine what the behavior is on this tool with the missing workspace. This is an odd behavior.

It may also be a good idea to open a Support Issue if this is repeatable behavior.

[MattHowe · Accepted solution]

Hi @RenatoSalvaleon3 , I tried moving the workspace to another location, selected it and it looks like it worked. I think it was a Danish letter in the file path that it didn't like. Anyway, seems ok now, appreciate the help.

[RenatoSalvaleon3]

It makes sense to me now. Thanks for letting me know your solution.

Every release we conitnue to improve our unicode support for various parts of the extension. We are not feature complete yet but the most recent one in Pro 3.4 is for folder and file paths for Quick tools. We'll continue improving in this part of the product.