|Intuitive UI configurable for many use cases|
|Add, edit and delete entries|
|No need to know SQL, all database management tasks, including creating tables, are handled automatically.|
|Write to a separate data set, original data is never changed|
Local deployment (on-premise or cloud) *
Active Directory authentication
|Tableau Server authentication|
|Any action regarding data or configuration is audited|
|Amazon Redshift *|
|Hyper Files (BETA)|
|Available REST API to submit data automatically|
* Although these analytical databases are fully supported they are not ideal for the Write-Back use case that is more operational (OLTP), using them can lead to performance issues.
Tableau has defined the concept of Networked vs Sandboxed extensions:
Write-Back does not fit directly on any of these categories in the sense that it runs on your local environment, and thus in a protected environment, but it does require access to another resource namely the database, that is used to store data sets. For you this means you have total control on what the extension can access as you can apply your own network policies.
Write-Back goal is to enable any user to submit data directly on a dashboard, this means we have to make some compromises to ensure its correct usage. By writing to a separate dataset and with the audit mechanism we are sure that, even though we are giving freedom for the Creators and Explorers to be creative and use Write-Back in different ways, the original data is never touched and we can always keep track of who did what. This detailed tracking can be very important in different reasons:
That is why a separate dataset is the best choice, since the extension is fully managing it Write-Back can ensure all the premises above despite of user actions. However this doesn't mean you cannot choose to blend these inputs with existing data by leveraging different mechanisms:
* Please be aware that these mechanisms can overlap existing data that might not be recoverable without restoring a data base backup, use them wisely implementing any particular validations required to ensure no data is lost inadvertently.