We rely on the init id in the TransformLifecyle event in the
collection and on the frontend to coordinate the events to their proper
datasets. I had an incorrect assumption, and did not realize that the
datasets passed down to transform.Commit would not have their
dataset.ID fields populated.
Instead, we need to pass down the InitID for the dataset (if it exists)
directly into the call to transform.Commit. The save path seems to
expect the the ID field NOT be passed in when we go to save the dataset,
which is why I did not choose to just ensure the dataset.ID field was
populated before passing the dataset down into transform.Commit.
It is not a problem if the InitID field is not populated, and it is
actually expected that this field is not populated for "apply" runs.
We rely on the init id in the
TransformLifecyleevent in the collection and on the frontend to coordinate the events to their proper datasets. I had an incorrect assumption, and did not realize that the datasets passed down totransform.Commitwould not have theirdataset.IDfields populated. Instead, we need to pass down the InitID for the dataset (if it exists) directly into the call totransform.Commit. The save path seems to expect the the ID field NOT be passed in when we go to save the dataset, which is why I did not choose to just ensure thedataset.IDfield was populated before passing the dataset down intotransform.Commit.It is not a problem if the
InitIDfield is not populated, and it is actually expected that this field is not populated for "apply" runs.