Skip to main content
Solved

Batch Deploy won't write to ArcGIS online

  • February 21, 2020
  • 5 replies
  • 35 views

anders_d
Contributor
Forum|alt.badge.img+1

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?

Best answer by rahulsharma

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

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • February 21, 2020

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"


anders_d
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • February 24, 2020

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.


rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • Best Answer
  • February 24, 2020

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


rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • February 24, 2020

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


anders_d
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • February 25, 2020

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.