Looking to Omit Price on Catalog Item, but does not save?

[Cory Hitchings]

Good morning, 

I am trying to add 7 new catalog items under a category and for some reason I cannot "Omit price in cart" on any of the items.  I check the box, click Save, click Update etc, and the box is becomes deselected.  We are running Madrid.  Am I missing something?  Any ideas?  Thanks! 

[Ben Rowny]

Check your form for a form section called "Pricing" with the "Omit price in cart" field on it -- if it's there, then it will be in two places on the form, which notoriously causes updates for that field to fail or not work properly.

Madrid re-does the layout of the Catalog Item form, breaking it up in to sections... BUT if you've configured the main section AT ALL, it will leave everything in the main section, so you'll end up with some fields on the form twice. I would strongly recommend *either*:

1. Revert the sc_cat_item form layout to out-of-box
or
2. Look through the form sections that Madrid has added - and remove any duplicates from the main form section.

[Cory Hitchings · Accepted solution]

Thanks very much for the response!  I changed the view to "Advanced view" and was able to save the 'Omit price in cart' checkbox!  Weird.  Thanks again! 

[Ben Rowny]

There is also a client script that attempts to hide the field based on the "Use Cart Layout" option - this kinda breaks if the field is on the form twice, so again, double check the configuration of the form layout if you can (or if you're not admin on your instance, have your admin do it).

[Allen Andreas]

Yea, this same issue was happening for me, but after looking things over it's because the field is on the form twice (once where I added it and have had it showing in prior versions of SN) and then also within the "Pricing" tab. Due to this, it was causing issues with saving.

I've marked your reply above browny as Helpful, thanks.

So while you can get around this by changing view to "Advanced", you'd have to remember to do this every single time you're building catalog items or pass this on to other admins, etc. and that's a bit of an unnecessary "maintenance" step.

The approach I went with and would recommend is to simply either remove the duplicate field from the core form view (so at the top and outside of any sections), or remove it from the Pricing tab section and then just learning to go to that new place only for marking it true (or false) accordingly.

For those reading this, since he marked his own reply as Correct...they would think that's the better approach and I wouldn't agree with that (even though technically it does work).

Thanks!