Carrier configuration for "showmethod" does not appear in carrier configuration

[matthew-muscat]

The carrier settings for the "showmethod" configuration field does not appear for both the standard Magento Shipping Methods (ie: free shipping / flat rate) as well as custom shipping methods.

Steps to reproduce

1. Install Magento CE 2.1.0.
2. Review the "Free Shipping" / "Table Rate" and/or "Flat Rate" method settings in "Stores / System / Configuration / Shipping Methods".
3. The setting "showmethod" (with the label "Show Method if Not Applicable") does not display, despite being specified in the "Free Shipping" method's adminhtml/system.xml file. @see

   magento2/app/code/Magento/OfflineShipping/etc/adminhtml/system.xml

   Line 147 in f10c7c8

   <label>Show Method if Not Applicable</label>

Expected result

The "Show Method if Not Applicable" setting should appear for the above carriers, as well as custom carriers.

Actual result

The "Show Method if Not Applicable" setting does not appear for the above carriers, as well as custom carriers.

• Changing the value of the "showmethod" field to "showmethod_test" allows the field to display - Is there some other logic tied to the display of this field in the admin area?

Sample code from custom carrier system.xml

<field id="showmethod" translate="label" type="select" sortOrder="170" showInDefault="1" showInWebsite="1" showInStore="0">
    <label>Show Method if Not Applicable</label>
    <source_model>Magento\Config\Model\Config\Source\Yesno</source_model>
</field>

<field id="specificerrmsg" translate="label" type="textarea" sortOrder="180" showInDefault="1" showInWebsite="1" showInStore="1">
    <label>Displayed Error Message</label>
    <depends>
        <field id="showmethod">1</field>
    </depends>
</field>

[viktym]

Thanks for reporting this issue @matthew-muscat
We've created internal ticket MAGETWO-59181 regarding this

[SerhiyShkolyarenko]

The fix is delivered to develop branch. Closing the issue.

[Ctucker9233]

@SerhiyShkolyarenko Will MAGETWO-59185 be included in 2.1.3?

[dcabrejas]

@SerhiyShkolyarenko can you confirm what version of Magento has this fix? I am having the same problem on 2.1.7.