5 - Exercise Summary

Solution

The image above depicts the part of the writeback infrastructure you’ve configured so far. You’ve synchronized backing datasets into the object storage service, built Ontology-aware applications, and configured writeback datasets for your object types. What you’ve not done yet is create actions that write back to the storage service or configured builds to keep the writeback datasets in sync with those edits. If you were to expand your object types in the Data Lineage graph, you’d see your connected writeback datasets as shown in the picture below.

What you built

• Writeback datasets for your flight alert and passenger object types.
• A writeback dataset for the join table backing your passenger ⟷ flight alert link type.

What you learned

• Once writeback is enabled for an object type, the corresponding writeback dataset should be considered the canonical data source for further Foundry work rather than the original backing dataset.
• If you want to enable link modification actions on many-to-many link types, you’ll need to add a writeback dataset to the backing join table.
• It is a best practice to only allow edits via Foundry Actions, though other configurations are possible.