[SalesForce] Order of values in a multi-select picklist is not consistent

I added a value to a multi-select picklist field. Then I reordered the value to fit it in the list. After this I opened a record of this object and added this new value.

When looking at it in the Salesforce GUI it looks as I expect, i.e. it is located in the correct order. But when querying the field of this record the new value is located on the last position.

EXAMPLE:
This is the way it looks (number 64) in the Salesforce GUI
10; 20; 30; 40; 50; 64; 100; 200; 300; 400; 500; 600; 700; 800; 900; 1000

When querying the record the field value displays like this
10;20;30;40;50;100;200;300;400;500;600;700;800;900;1000;64

This is important since I use the values of this record as a key document for use in a portal. Any clue why this happens?

I have tried to clone the record, but no difference.

Regards / Niklas

Best Answer

As far as the database is concerned, the values were simply entered in the order they were created. What you've done is tell SF to change the order in which they're displayed in the GUI. That's why they query results will return the order in which they were created instead of the order in which you've told the GUI to display them. The query is simply querying the memory locations and not the GUI.

Related Solutions

[SalesForce] Is it possible to map picklist values to some other text or number field just like standard Opportunity Stage field

Binding picklist values to other behavior has a bunch of less-than-optimal-for-maintenance solutions:

Custom settings as you mentioned
Apex static constants plus triggers and/or VF controllers
Custom objects (akin to custom settings solution)
Encoding the value in the picklist item itself as in "Positive [5]", "Negative [0]" and using string functions/formulas to grab the scores
Using workflow field update formulas to update the Contact.score based on values in the picklist

Item #4 works OK except when the score changes for a given value - in this case, you have to decide what to do about legacy data.

If you use Item#1,2,3 you can use validations to inform the user/sysad that some aspect of the maintenance was omitted

[SalesForce] How to remove the selected values from multi select picklist

Ok, so assuming you have just completed step 1, you have a large list in picklist 1 and a smaller list in picklist two.

I'm also assuming that you are using databinding in lightning are are not directly manipulating the DOM

Given these conditions, run your first list through this function. It will remove any dupe values already in the second list:

xorSourceItems : function(source,dest) {
  var itemsToReturn = [];
  source.forEach(function(sourceItem, sourceIndex) {
    var match = false;
    dest.forEach(function(destItem, destIndex) {
      if (destItem.value == sourceItem.value) {
        match = true;
      }
    });
    if (!match){
        itemsToReturn.push(sourceItem)
    }
  });
  return itemsToReturn;
}

Best Answer

Related Solutions

[SalesForce] Is it possible to map picklist values to some other text or number field just like standard Opportunity Stage field

[SalesForce] How to remove the selected values from multi select picklist

Related Topic