Please always try freshest version available (namely 2.1.8 in this case) prior to issue report. This could have been fixed in 048d2e6991d964f8ee770a3377cc5fde62802f63.
Hello, Please help me for resolved this issue.
Please check if the issue is still reproduced if you upgrade to 2.1.8.
I need to resolved this issue on magento 2.1.4 version.
This is not a recommended way, you can try to apply commit I mentioned or other related to fix changes at your own risk though.
Issue shall be closed if it is not reproducible on latest 2.1.x version.
Our current site is live, In this site most of the customers and orders So we can not upgrade this site. Please give me another way for resolved this issue.
Of course you should not upgrade production site. Just use your staging/local environment to check it and then deploy to production.
The ultimate way to obtain fixes is version upgrade. Old version bug reports are out of scope for this repository.
@Jalondhara you could replace the 2.1.4 class with implementation put mentioned by @orlangur using custom module and DI or use plugin as it's public method, but it would be done on your own risk as said above and upgrade is recommended.
No sign the issue is reproducible on 2.1.8.
Most helpful comment
Of course you should not upgrade production site. Just use your staging/local environment to check it and then deploy to production.
The ultimate way to obtain fixes is version upgrade. Old version bug reports are out of scope for this repository.