This content is also available at learn.palantir.com ↗ and is presented here for accessibility purposes.
📖 Task Introduction
Once you’ve identified the writeback actions you want your end users to take through your application interfaces, the next step is to configure writeback datasets that can contain the data edits those actions will generate (e.g., priority on alert 123 is changed from medium to high).
Let’s start by creating a writeback dataset for your flight alert and passenger object types.
🔨 Task Instructions
Open your flight alert object type in the Ontology Management App (OMA).
From the left-hand menu, click the Datasources menu item.
Click the green ⊕ Generate button in the Edits block to the right.
A Foundry explorer window appears suggesting a name and save location for your writeback dataset.
Save the writeback dataset in the same location as your backing dataset. By default, the writeback dataset name is the name of the backing dataset appended with _edited.
Click the blue Save button.
At the bottom of the Edits block, toggle on the option to "Only allow edits via actions."
Save the changes to the Ontology by clicking the green Save button in the top right of the application.
Now, repeat this step for your passenger object type.
📚 Recommended Reading (~1 min read)
Review how to enable edits through Actions vs other means in Permissions.