Unable to add custom Data Interoperability format (*.fds) to ArcCatalog 10.8.1

746
2
Jump to solution
12-01-2020 10:11 AM
EricAnderson_DHS
Occasional Contributor

Hello,
 
We're unsure of when this issue started, but we are no longer able to import a custom format file (*.fds) to a Data Interoperability connection within ArcCatalog 10.8.1. The workflow we use is: 

  1. Open ArcCatalog and ensure Data Interop extension is assigned
  2. Interoperability Connections folder > Format drop-down > More Formats
  3. Import custom .fds file
  4. Looks successful, but does not show up in list of custom formats in the FME Reader Gallery window

 
This is causing an issue where the associated *.fdl file is not previewing any data (geography or attributes). Again, we're not sure exactly what changed which caused this issue or when exactly it started, but we've been using this custom format file for many years without any issue. 
 
Since it appears to add the custom format successfully, are there any additional logging we should review to figure out what is failing?

0 Kudos
2 Solutions

Accepted Solutions
BruceHarold
Esri Regular Contributor

Hello Eric.  Can you please manually copy the fds file into your profile directory C:\Users\<username>\Documents\FME\Formats, refresh your fdl connection and check your fdl files contain data?  Let me know directly via bharold at esri dot com, thank you.

View solution in original post

EricAnderson_DHS
Occasional Contributor

While not the actual solution mentioned here, Bruce was able to help us rebuild the fds file using a sample schema KML file originally used as the input. Thanks a whole bunch Bruce! 

View solution in original post

0 Kudos
2 Replies
BruceHarold
Esri Regular Contributor

Hello Eric.  Can you please manually copy the fds file into your profile directory C:\Users\<username>\Documents\FME\Formats, refresh your fdl connection and check your fdl files contain data?  Let me know directly via bharold at esri dot com, thank you.

EricAnderson_DHS
Occasional Contributor

While not the actual solution mentioned here, Bruce was able to help us rebuild the fds file using a sample schema KML file originally used as the input. Thanks a whole bunch Bruce! 

0 Kudos