C&P Settings isn't saving any of my record type mappings!

[Louise Kelly]

Hello - we have been using a number of opportunity record type mappings in C&P settings. When we upgrade to 8.6 (from 8.2) I noticed that in the new Opportunity tab in C&P settings that all my mappings were now showing a condition of 'if sku is blank' (where before it had had an actual SKU value). I have been trying to re-create all the SKU -record type mappings but every time I get out of the C&P settings tab it loses all the mappings. Here is a picture of what is happening:

1. I set up my SKU - record type mappings:


2. After I leave the C&P Settings tab and then come back, here is what I see:



I also know for sure that the mapping isn't working because I tested using a checkout page and the opportunity didn't have the right record type (and didn't go to the right campaign either!)

I should also note that I did go through all the post-installation instructions after I upgraded even though the upgrade was a minor one. Please help - we use these mappings all the time!

[Louise Kelly]

A small update to this:
I just did more testing, and it looks like the mapping actually DOES work (when I submitted more transactions via a checkout page, the opportunities came in with the correct record type). However, we still have a problem because when you go to the oppportunities tab of the C&P settings, it's still showing all of these as 'if sku is blank' options. The biggest problem with this is that if you go to make any other changes to the opportunity page of C&P settings, it tells you that there are duplicates and won't let you save anything. I saw another post from someone who appeared to be having the same issue - you had asked to get permissions to his/her instance and hadn't gotten them yet. I bet it's the same problem. It's compounded by the fact that on my small laptop screen I couldn't even see the 'delete' button on the right hand side of the SKU mapping items (one thing I tried was deleting all the mappings and then recreating them).

But bottom line - the way it works right now, the only way to make the SKU mappings work is to re-fill all the SKUs every time you want to add a new SKU mapping. Not fun. Please fix!

[CnP.Support]

Good day!

We are not aware of any such issues. The latest release addressed one issue raised by one client that had over 900 maps and saving was taking a long time so we changed the way validations are done. We had never considered a case of someone having 900 SKU maps but it was fixed in the latest release.

We can review your instance to see what you are referring to. Please grant us access so we can review your instance.

How to grant access:http://bit.ly/Salesforce-Grant-Access

[Louise Kelly]

Hi - I just granted you access. Here's our org id: 00DE0000000cTUB

We definitely don't have that many mappings - only around 10. Looking forward to hearing back from you - thanks.

[CnP.Support]

Good day!

We tested your instance and all works as expected. We added an entry and updated/deleted without any issues.

You may wish to join the office hours and explain what your expectations are so we can match it against the system's capabilities.

[CnP.Support]

Good day!

Thank you for joining the office hours and clarifying the post.

As stated it appeared to be an installation issue. We fixed it for you.

The problem was the "SKU IS" filter was not updated during the installation and as such was missing. It is strange that Salesforce installation process at times misses certain updates.

Please test it and let us know if we can be of any further assistance.

[Louise Kelly]

Everything is fixed!

Thank you so much - just went in and tested and now it is saving the SKU - record type mappings perfectly. Thank you!