The content on this page explains how to maintain a data store after you've created it.
For information on creating one, see: Data Stores
All data store attributes can be edited by users with editor or administrator rights. The following list details how to edit each attribute:
After making any of the above edits, you may either save a draft or publish a new version of the data store. To save a draft, click "Save Draft." Saving a draft does not affect the environment or execute SQL DDL statements, but you may come back to the data store at any time to view and publish the changes. To publish a new version of the data store, follow these steps:
No matching tables found!
See also: Editing a Custom Data Type
Take care when deleting a data store not to disrupt any active processes that query or write to the data store.
System Administrators have the ability to delete data stores (and other objects) in bulk by selecting them and clicking Delete in the toolbar.
A user must have at least Viewer permissions to a data store in order to use its entities to query, write, or delete data.
The security role map of a data store controls which users can see or modify it and its properties. By default, only the data store creator and system administrators have access to the data store. See Editing Object Security to modify a data store's security.
The following table outlines the actions that can be completed for each permission level in a data store's security role map:
|Retrieve entity to read/write at runtime*||Yes||Yes||Yes|
|View the data store definition||Yes||Yes||Yes|
|Update the data store definition||Yes||Yes||No|
|View the security||Yes||Yes||No|
|Update the security||Yes||No||No|
|Delete the data store||Yes||No||No|
|Save & Publish the data store||Yes||No||No|
*Users must have at least Viewer permissions to the data store in order to read or write data using the Write to Data Store smart service.
On This Page