Datasets added while in "Edit in Dialog" mode do not appear in test run

Description
When using Call Test, adding a dataset at the step level of the called test step via “Edit in Dialog” is saved/visible on the Test, but it does not propagate to the Test Run in the Test Execution. If the same dataset is added by directly editing the called test step (outside “Edit in Dialog”), it appears correctly in the execution.

Pre-conditions

• Two Tests exist:
  • <called test> with a test-level dataset (example: RTEST-18842)
  • <parent test> that calls <called test> (example: RTEST-10668)

How to reproduce

1. Create a Test <called test> and define a test-level dataset.
2. Create another Test <parent test> that calls <called test>
3. Open <parent test> and click Edit in Dialog.
4. On the step that calls <called test>, add a dataset (step-level) via Edit in Dialog.
5. Save the step.
6. Save and exit Edit in Dialog.
7. Confirm the call step appears blue (dataset saved indicator).
8. Add <parent test> to a Test Execution.
9. Open/run <parent test> from the execution (Test Run).

Actual result/Attachments

• In the Test Execution (Test Run), the dataset on the call step is shown, but the added dataset variable is missing (not applied/available).

• The dataset appears on the Test side but not on the execution side.

• [^2026-01-14_07-48-42.mp4]

Expected result
Adding a dataset to the call step via Edit in Dialog should behave the same as adding it via direct step edit: the dataset/variables should be available and correctly reflected in the Test Execution (Test Run).

Workaround
Delete the dataset added via Edit in Dialog and re-add it by directly editing the called test step (outside Edit in Dialog).