Select to view content in your preferred language

Quick Export : can't save connection

380
4
Jump to solution
01-21-2025 09:59 AM
RémyGourrat
Occasional Contributor

Hi,

In Pro 3.3, i set a snowflake connection. Test is successfull.

But when i want to save, i have this message => Unable to store Connection Unable to add connection 'TEST'

Where Pro want to save it ? in a file ? do you know the location ?

Thanks for your help

Rémy

0 Kudos
1 Solution

Accepted Solutions
BruceHarold
Esri Regular Contributor

Sorry I was not clear, if you start the Workbench application from the Analysis ribbon or ArcGIS program group then you'll see the Tools>FME Options>Default Paths dialog.

I think I see a bug though, while database connections persist for the Workbench app they do not for Quick Translate or the system Quick Import tool - I will investigate.

View solution in original post

0 Kudos
4 Replies
BruceHarold
Esri Regular Contributor

Remy, I think this applies to Pro 3.3, if not please reply, but in the Tools>FME Options>Default Paths control you will see your connection storage options.  You must have permissions for these locations.

https://docs.safe.com/fme/2024.1/html/FME-Form-Documentation/FME-Form/Workbench/options_default_path...

 

0 Kudos
RémyGourrat
Occasional Contributor

Hi Bruce,

i don't have FME on my PC, just only ArcGIS Pro 3.3 with the DataInterop Extension.

i don't see a menu to access DataInterop FME path location in ArcGIS Pro,

have you an idea ?

 

0 Kudos
BruceHarold
Esri Regular Contributor

Sorry I was not clear, if you start the Workbench application from the Analysis ribbon or ArcGIS program group then you'll see the Tools>FME Options>Default Paths dialog.

I think I see a bug though, while database connections persist for the Workbench app they do not for Quick Translate or the system Quick Import tool - I will investigate.

0 Kudos
RémyGourrat
Occasional Contributor

Hi Bruce,

Thanks for you work around by workbench, i can save in workbench. But it's not showed in quick export/import.

Esri support tell me it's a bug the issue closed in Pro 3.5