
It looks like the empty fields are not included in the post request, which they should, since removing values is just as important as setting them :-)
This is a known issue, internal ticket id MAGETWO-57226. Thanks for posting
@Corefix Update to 2.1.1. and report back or close this ticket otherwise.
It still not works in 2.1.1. I will create a ticket on the partner portal as well. (hopefully it will get more priority)
Still not works in 2.1.3
@seavenger this patch works for me: https://github.com/magento/magento2/pull/6899
patch didn't work for me on 2.1.2
@roseofgold
are you sure you applied it correctly?
We are using it in a production system without any issues.
@nagno No I'm not sure. I just tried applying it again and now I can't use my admin :(
@roseofgold your issue is probably not related to this patch or you have an interfering customisation.
If you check the comments on the patch, @wigman created a 2.1.3 compatible version as well.
@nagno thought you might like to know (and for posterity) that it works for me in IE11 but not in Chrome (v55). It's probably some customization that causing problems as it works differently in different browsers.
@roseofgold It is not working for us in any browser (even in a Vanilla Magento environment). It is still not working in 2.1.5.
Progress so far: we got one not working patch from the support team and another one, which was breaking the attribute set change functionality (you wasn't able to select an attribute set for new products as well).
@nagno Updating to 2.1.6 broke it all browsers and all environments. I believe this issue should not be closed.
Seems like duplicate of #6253 #7687 #4545
and that this is fixed by
https://github.com/nagno/magento2/commit/b380502570b92449326ab6ed50e6ce0359287240
Still experiencing this issue in 2.1.4
@Corefix, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.
We tested the issue on 2.3.0-dev, 2.2.0, 2.1.9
Of course you are not able to reproduce it, because it was fixed in 2.1.8. (See changelog for 2.1.8)
I did report it in October 2016 via the partner portal and after 2 not working patches Magento finally fixed it. It took about 9 months to provide it even with "priority" partner portal support...
This issue still persist in Magento ver. 2.2.2
I Found Solution after R&D On Magento database.
Login In your phpmyadmin
Go to your website database
Open "eav_attribute" table
Find Your multiselect "attribute_id"
Edit Row
If "backend_model" Column blank then paste this Magento\Eav\Model\Entity\Attribute\Backend\ArrayBackend
And Also Please check this
https://magento.stackexchange.com/questions/224621/warning-array-filter-expects-parameter-1-to-be-array/230444#230444
Most helpful comment
It still not works in 2.1.1. I will create a ticket on the partner portal as well. (hopefully it will get more priority)