Esri ArcGIS Server Feature Service Writer Parameters
Connection
Specify the fully-qualified URL for the Feature Service.
Ensure that the URL is for a valid Feature Service, and does not point to a specific layer or table inside a Feature Service, (that is, the URL should not end with /0).
If the Feature Service requires authenticated access, specify the authentication type required by the server. The available options are:
- None – Access the Feature Service anonymously. This is the default.
- Provide Token – Use a given ArcGIS token.
- Basic – HTTP Basic authentication.
- Digest – HTTP Digest authentication.
- NTLM – Also known as Integrated Windows Authentication (IWA). Authenticates using a given username and password.
- Kerberos – Also known as Integrated Windows Authentication (IWA). Authenticates as the current Windows user. This option is supported only on Windows systems connected to a domain.
If the Authentication Type is Basic, Digest, or NTLM, specify the username.
the Authentication Type is Basic, Digest, or NTLM, specify the user’s password.
If the Authentication Type is set to Provide Token, specify the token here.
Advanced
This parameter specifies the maximum number of features that may be present in a single response from the server. Reduce this value if reads are failing due to timeouts.
The value for this parameter is capped to the maxRecordCount property on the Feature Service.
If this parameter is not provided, it defaults to 1000. If the operation is set to Upsert, the parameter value used will be either 10000 or the user-provided value, whichever one is larger.
This parameter specifies whether Global IDs are to be used as the primary key for write operations, instead of Object IDs. This behavior may be necessary to use some ArcGIS features, such as Feature Service Sync.
When this parameter is set to Yes, it remains possible to insert features without a value for the Global ID attribute.
If this parameter is not provided, it defaults to No.
When Use Global IDs is set to Yes, this parameter determines the behavior during Insert/Upsert operations when a feature without a Global ID value is encountered.
- Yes – An error is raised if the feature does not have a Global ID. This is the default behavior for workspaces created before FME 2020.2.
- No – Auto-generated Global IDs are assigned to features without one.
Prior to FME 2022.0, web access through this format would automatically disable HTTPS Certificate verification when an SSL Error was received from the server. Now, this behavior must be explicitly enabled or disabled by this parameter.
The value of this parameter takes priority over the value of the Verify SSL Certificates parameter which might be defined by the Web Connection used with this format.
When Asynchronous Writes is set to Yes, the writer will send write requests without waiting for the status of the previous write request. For translations with many features, this can reduce the time that the workspace spends running. However, when in this mode, the status of write requests made will not be reported until all features have been written.
The value of this parameter is only used when writing to – not overwriting – an existing feature server. If the writer is creating a new feature service/overwriting an existing feature service, then this parameter will not be used.
- Yes – Perform writes in asynchronous mode. The feature service being written to must support asynchronous writes.
- No (default) – The status of each write request is reported before a new write request is filed.
When Asynchronous Writes is set to Yes, this option can be used to set whether the writer will poll for the status of each async write request after all features have been created.
- Yes (default) – The writer polls for statuses up to the timeout period defined. If a single write request failed, the translation will stop. Write requests which are still pending will not be treated as failures.
- No – The status of write requests is not reported. If write requests have failed, these will not be logged and the translation will proceed.
When Report Asynchronous Write Statuses is set to Yes, this parameter determines the maximum number of seconds the writer will poll for the status of write requests.
Default: 300