Hello everyone,
I’m currently facing a challenge when trying to modify multiple values in a Table View using a CSV import via an Action, due to certain constraints.
What I’m trying to achieve:
We want to implement a workflow where users can maintain a master dataset. This master dataset is initially generated automatically by a logic (residing in a Foundry Dataset) and then requires manual maintenance by a dedicated team. The workflow is envisioned as follows:
-
A user exports a specific object table from Workshop as a CSV.
-
The user modifies the necessary parts of the CSV locally.
-
The user then imports this modified CSV back into the Table View via an Action to update the master data.
The Problem:
When performing a ‘modify’ action via CSV import within the Table View’s Action, all values in the CSV, even those identical to existing values in the object, are treated as updates and overwrite the existing data. This leads to unintended modifications in some columns where the user’s intention was not to change the value, and consequently, updates from the backend pipelines are not reflected correctly.
Specific Clarification on “unintended modifications”:
My concern is that if a column in the imported CSV has the exact same value as the existing object property, the Modify Action still processes it as an “overwrite” operation. This means we cannot differentiate between an intentional change and an unintentional “same value” update, which can interfere with subsequent pipeline update logic.
My Question:
Is there a way, when using a modify action via CSV import in the Table View’s Action, to prevent overwriting values that are identical to the existing ones? I have already tried settings like disable in the override configurations, but they don’t seem to work as expected for CSV import scenarios.