Magento 2.4.4 store view system config issue

[jorgehs91]

Preconditions and environment

• I'm using Magento CE 2.4.4.
• I tested with a clean installation.
• Field enabled must be hidden in all scopes, except Default Config.

As precondition, I'm using the following system.xml and config.xml in a custom module.

<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Config:etc/system_file.xsd">
    <system>
        <tab id="testing" translate="label" sortOrder="10">
            <label>Testing</label>
        </tab>
        <section id="testing" translate="label" sortOrder="90" showInDefault="1" showInWebsite="1" showInStore="1">
            <class>separator-top</class>
            <label>Testing</label>
            <tab>testing</tab>
            <resource>Magento_Catalog::catalog</resource>
            <group id="tracking" translate="label" type="text" sortOrder="10" showInDefault="1"
                   showInWebsite="1" showInStore="1">
                <label>Tracking</label>
                <field id="enabled" translate="label" type="select" sortOrder="10" showInDefault="1" showInWebsite="0"
                       showInStore="0">
                    <label>Enabled</label>
                    <source_model>Magento\Config\Model\Config\Source\Yesno</source_model>
                </field>
                <field id="emails" translate="label" type="text" sortOrder="20" showInDefault="1" showInWebsite="1"
                       showInStore="1">
                    <label>List of emails</label>
                    <depends>
                        <field id="enabled">1</field>
                    </depends>
                </field>
            </group>
        </section>
    </system>
</config>

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Store:etc/config.xsd">
    <default>
        <testing>
            <tracking>
                <enabled>1</enabled>
            </tracking>
        </testing>
    </default>
</config>

Steps to reproduce

1. In admin, go to Stores > Configuration;
2. Make sure you are under Default Config or Main Website scope;
3. On left tabs, look for tab Testing and click in Section Testing;
4. Now, change the scope to Default Store View (or any other store view scope).

Expected result

Is expected that the field List of emails is visible and readonly, like the Main Website scope.
The image below shows what is expected.

Actual result

The field List of emails does not show, preventing me to change the field value in Store View scope.
The image below shows the actual result.

Additional information

No response

Release note

No response

Triage and priority

• 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 @jorgehs91. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• 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, join the Community Contributions Triage session to discuss the appropriate ticket.

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

[ravendra1990]

Please Use below code in system.xml file
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Config:etc/system_file.xsd"> <system> <tab id="testing" translate="label" sortOrder="10"> <label>Testing</label> </tab> <section id="testing" translate="label" sortOrder="90" showInDefault="1" showInWebsite="1" showInStore="1"> <class>separator-top</class> <label>Testing</label> <tab>testing</tab> <resource>Magento_Catalog::catalog</resource> <group id="tracking" translate="label" type="text" sortOrder="10" showInDefault="1" showInWebsite="1" showInStore="1"> <label>Tracking</label> <field id="enabled" translate="label" type="select" sortOrder="10" showInDefault="1" showInWebsite="1" showInStore="1"> <label>Enabled</label> <source_model>Magento\Config\Model\Config\Source\Yesno</source_model> </field> <field id="emails" translate="label" type="text" sortOrder="20" showInDefault="1" showInWebsite="1" showInStore="1"> <label>List of emails</label> <depends> <field id="enabled">1</field> </depends> </field> </group> </section> </system> </config>

[jorgehs91]

Hi @ravendra1990, thanks for comment, but one thing that I missed to describe, is that I don't want to show the enabled field in store view and website scope.
I'll update my issue to describe this.

[ravendra1990]

hi @jorgehs91 I think issues persist because of the
<depends> tag. Your Email Field is depend on the enabled fields.
If you will remove the that tag it will work


.

[jorgehs91]

Hello @ravendra1990, thanks for helping.
However, do you agree this behavior could be a bug, since we can't use depends to a field that is not shown in given scope?

[jorgehs91]

Important to say that this was working properly on 2.3.

Another problem, probably related to this one, is occuring when the store view scope field is set to Use Default. The value is returned as NULL.

This screeshot was taken from Dotmailer module.

[m2-assistant]

Hi @engcom-November. 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-November]

@jorgehs91,
Thank you for the reporting and collaboration!
We have tried to reproduce the issue in Magento 2.4-develop branch and the issue is reproducible for us with the steps mentioned in the main description.
Hence confirming the issue.
Thanks