Solved

Batch Deploy won't write to ArcGIS online

  • 21 February 2020
  • 5 replies
  • 5 views

Badge

When trying to Batch Deploy my simple Geopackage files to AGOL the 'Next' button never gets possible. It wants a path to the files to be written. Is it not possible to use Batch Deploy to upload to AGOL or what am I missing?

icon

Best answer by rahulsharma 24 February 2020, 20:20

View original

5 replies

Badge +10

Hi @anders_d

 

You can use Dynamic and Write for both Geo package and AGOL to upload data

For ArcGISONLINEFEATURE write, set the following feature type properties

Select "Dynamic Schema Definition"

Geometry should be set to "From Schema Definition"

Schema Source: "Schema From Schema Feature"

Badge

Hi @anders_d

 

You can use Dynamic and Write for both Geo package and AGOL to upload data

For ArcGISONLINEFEATURE write, set the following feature type properties

Select "Dynamic Schema Definition"

Geometry should be set to "From Schema Definition"

Schema Source: "Schema From Schema Feature"

I have no problem running the workspace. It's the Batch Deploy that won't be setup and saved.

Badge +10

Hi @anders_d,

 

Unfortunately, Batch Deploy is a bit old now, as it is from a time when FME was mostly Files and folders data types and no Web Services were involved. That is most likely the reason why the "Next " button is disabled ( I can investigate this with our dev team).

 

Workaround

In your case, the best solution is to use Workspace Runner solution which will have 2 workspaces

 

1. Control Workspace (Pass the name of each file)

2. Processing Workspace (upload the data to AGOL)

This article is good start point https://knowledge.safe.com/articles/1469/batch-processing-using-the-workspacerunner-1.html

Badge +10

I have no problem running the workspace. It's the Batch Deploy that won't be setup and saved.

Hi @anders_d,

 

Unfortunately, Batch Deploy is a bit old now, as it is from a time when FME was mostly Files and folders data types and no Web Services were involved. That is most likely the reason why the "Next " button is disabled ( I can investigate this with our dev team).

 

Workaround

In your case, the best solution is to use Workspace Runner solution which will have 2 workspaces

 

1. Control Workspace (Pass the name of each file)

2. Processing Workspace (upload the data to AGOL)

This article is good start point https://knowledge.safe.com/articles/1469/batch-processing-using-the-workspacerunner-1.html

Badge

Hi @anders_d,

 

Unfortunately, Batch Deploy is a bit old now, as it is from a time when FME was mostly Files and folders data types and no Web Services were involved. That is most likely the reason why the "Next " button is disabled ( I can investigate this with our dev team).

 

Workaround

In your case, the best solution is to use Workspace Runner solution which will have 2 workspaces

 

1. Control Workspace (Pass the name of each file)

2. Processing Workspace (upload the data to AGOL)

This article is good start point https://knowledge.safe.com/articles/1469/batch-processing-using-the-workspacerunner-1.html

Great! I made it work with the Workspace Runner as controlling.

Thanks for the guidance.

Reply