You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, `process`**replaces** the child workspace LDM with the declarative fragment built from your inputs. Any prior custom datasets or date instances that aren't in the current call are lost.
138
+
139
+
Set `merge_into_existing_ldm=True` to switch to an **append / update** behaviour: `process` loads the current workspace LDM first, replaces any dataset or date instance whose `id` matches one in your input, and keeps the rest of the model as is (including previously uploaded custom extensions).
140
+
141
+
Optional cleanup: when `remove_managed_datasets_missing_from_input=True` and `management_tag` is set, datasets that carry that tag but are **not** in the current `process` call are removed from the merged LDM before the upload. This lets tools such as BCA reliably delete their own obsolete custom datasets without touching anything else.
142
+
143
+
```python
144
+
ldm_extension_manager.process(
145
+
custom_datasets=custom_dataset_definitions,
146
+
custom_fields=custom_field_definitions,
147
+
check_relations=False,
148
+
merge_into_existing_ldm=True,
149
+
remove_managed_datasets_missing_from_input=True,
150
+
management_tag="bca_tooling_managed",
151
+
)
152
+
```
153
+
131
154
## Example
132
155
133
156
Here is a complete example of extending a child workspace's LDM:
0 commit comments