Improving Data Refresh Between Write-Back and Transformed Object in Workshop

Ask the Community
,
1

Hi everyone,
I have a question regarding improving data freshness in a Workshop setup involving multiple objects:

  • I’m using Object2 in an Object Table within the Workshop.

  • Users interact with Object1 (e.g., to create records via Workshop actions). These changes are written back to Object1’s writeback dataset.

  • I then perform a transform that takes Object1’s writeback data and produces a new dataset, which is used to create Object2.

  • This means the Workshop displays data through Object2, even though the user-created records originate from Object1.

The issue: after a user creates a new record through Object1, it takes about 5 minutes for that change to appear in the Object2 table within the Workshop

is there a best practice for syncing newly created records more quickly across objects in a Workshop?

2

Hi @RubeM

You can set your action to recalculate variables on successful completion. But if you are first writing to a dataset and then using that dataset to update an object, this requires several Spark transactions to run, which adds delay – inevitable, since you’re updating the very foundation of your Object2.

How come you are using the write-back dataset to do the object creation, rather than just creating the object directly via a call to the Ontology API? Your function for Object1 can likely create Object2 as well, if this object is always created when Object1 is created.