To access feature type format parameters, open the Feature Type Properties dialog by clicking the properties 
button on a feature type in the workspace.
These parameters apply only to a selected feature type, not to the entire writer.
Tip: If a feature type parameter listed here conflicts with a writer-level parameter, then the writer parameter will be ignored and this feature type parameter will be used.
Table Settings: General
Table Handling (List Handling)
Controls how the feature type handles destination tables or lists. These options are available:
- Use Existing: If destination table/list does not exist, the translation will fail.
- Create If Needed: Create destination table/list if it does not exist.
- Drop and Create: Drop destination table/list if it exists, and then create it. If no features are written to the corresponding feature type, then the table will not be deleted.
WARNING: Only server administrators can delete tables. Deleted tables cannot be recovered – all data is lost.
Database Creation
New Database Permissions
Specifies the permissions to be used for newly created tables.
- All Users (default setting): Table will be modifiable by any user who is logged in.
- Admin Users: Table will be modifiable only by administrative users.
- Public: Table will be modifiable by anyone, even those who are not logged into an account.
Use GeoJSON Specification
Determines whether or not newly created tables will be interpreted as containing valid GeoJSON.
If the new table is intended to contain data other than GeoJSON, set this parameter to No.
Advanced
Document Source
The source of JSON documents to write to the database.
- Feature: Documents will be created from features sent to the Cloudant Writer (which is the usual behavior).
- JSON Attribute: Documents will be created using JSON directly from an attribute, if possible.
Document ID Attribute
This parameter is enabled when the Document Source is Feature. It can be used to specify an attribute to use as the Document ID. Any features that contain that attribute will use its value as the JSON Document ID. If not specified, the document ID will be automatically generated.