Error: The Update button is disabled. Customer Class Update

Is the Customer Active?

​@mblassingame35 yes. 

I would try to update that Customer manually and see if you get the same error. That might give you a better error, or you could use the Trace to see what is causing the error.

manually no problem at all. Just the mass update is the issue. Trace doesn't give me anything. 

When you change the Class on a Customer, there is a pop-up box that happens where you have to select Yes or No. I am not sure you can do this with a Mass Update.

I believe it is that box. But why present an option if it cant be done. 

It might be possible to change the behavior of the screen to default to either ‘Yes” or ‘No’ through a customization. If this was implemented, it would be possible to change the customer class through the mass update option.

Since that dialog box exists, and there is no default selection, your classes will need to be updated through an import scenario where you can define if the answer is “Yes” or “No” for that box.

This is a fairly simple data update if you wanted to try your first import scenario.

To update these customers, all you need to do is create an excel spreadsheet with two columns. One column for customer ID and the 2nd with the NEW customer class (I used price class below, just swap for customer class). Only include customers that you want to update in this list. 

You would then create a new data provider through the data provider screen with the Provider type of Microsoft Excel and give the provider a name. Attach the file to the data provider. Your screen should look like below...

From the schema tab, Click on these buttons in this order, then save. The source object will be the name of your excel sheet.

Your import scenario will look like below.. The provider will be the name of your data provider and object will be the active excel sheet.

Once your import scenario matches above, you can run through the “import by scenario” screen. It’s always good to click the toggle activation button and only run one record for the first run to make sure everything worked correctly. It’s also a good idea to try this in a test tenant first as you should be cautious about impacting live data.