Dynamic row system config default values were reset, lost when Enabled/disabled by dependencies fields

[tuyennn]

Preconditions (*)

1. Magento 2.4.2

Steps to reproduce (*)

1. Add a dynamic row system config depends on a main Yes/No configuration
2. Add values for dynamic row system config
3. main Yes/No configuration set: Yes => Save configuration. Check the database: core_config_data
4. main Yes/No configuration set: No => Save configuration. Check the database: core_config_data
5. main Yes/No configuration set: Yes => See the values for dynamic row

Expected result (*)

1. the values for dynamic row after set back to Yes must remain the values that were set before

Actual result (*)

1. Lost values for dynamic row config, the values on core_config_data is []

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @tuyennn. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[lano-vargas]

I get the same issue with when adding new column to an existing and all previous data row doesn't get rendered, not lost it still in core_config_data table but I assume because the new column isn't in the array it just won't rendered at all is this another issue can anyone confirm ? Thanks

[tuyennn]

@lano-vargas The problem is the fields are not gonna send the values to database while it was disabled. For now I set another template based on vendor/magento/module-config/view/adminhtml/templates/system/config/form/field/array.phtml for the Block extended Magento\Config\Block\System\Config\Form\Field\FieldArray\AbstractFieldArray.

And remove the id from the <table class="admin__control-table"> so it still sends value even with its dependencies disabled
Not sure the problem but just a workaround

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

We are able to reproduce the issue and hence confirming the issue.

On creation of dependant field dynamic row system config:

core_config_data table status at this point:

Disable the controlling field(parent field) from admin panel and save config:

database table:

Enable the controlling field again in admin panel:

database table:

[magento-engcom-team]

@engcom-Bravo Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!