{"id":171,"date":"2009-11-11T10:42:00","date_gmt":"2009-11-11T05:12:00","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=171"},"modified":"2009-11-11T10:42:00","modified_gmt":"2009-11-11T05:12:00","slug":"issues-with-deleting-a-picklist-option-from-a-picklist-attribute","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2009\/11\/issues-with-deleting-a-picklist-option-from-a-picklist-attribute\/","title":{"rendered":"Issues with deleting a picklist option from a Picklist attribute"},"content":{"rendered":"

CRM allows you to add\/update\/delete the picklist options of a picklist attribute. However, like most other contact managers that store the text\/reference of the deleted picklist option in the records where it had been used, CRM does not store the reference. It differs in this regard. Once a picklist option has been deleted, all existing records that had used this value would be reset to \u201cDefault Value\u201d.<\/p>\n

While checking out the picklist option sequencing in detail to explain it to our customer we found that CRM by default will always bring back the value of the deleted option.<\/p>\n

Here we take an example of Contact record and \u201cLead Source\u201d picklist attribute.<\/p>\n

1. We have added a pick list value with name \u201cTest\u201d in lead source picklist.
<\/span><\/p>\n

\n
\n
\n
\n
\"\"
2. Now we have selected the test option in a contact record.
\"\"
3. Now we go ahead and delete the \u201cTest\u201d option from \u201cLead Source\u201d..
\"\"
4. If you go back to the contact record that had this value assigned to it, it would now have been reset to \u201cDefault Value\u201d<\/p>\n

\"\"
Now unless you save this record, it would automatically get the next option that you add with the same \u201cValue\u201d.<\/p>\n

Another point worth mentioning is that if you had deleted one of the picklist options and published the customizations, the next time you add a new option to this picklist it would bring back the value of the deleted option. The value is editable in CRM 4.0 so make sure you change this value unless you were adding this as a replacement to the earlier deleted option. <\/span><\/div>\n

<\/p>\n

\"\"
Now we have deleted the test and publish the entity.<\/p>\n

In below screen shot we are adding a another picklist option \u201cTest123\u201d, it will bring up the same value as that of \u201cTest\u201d the deleted option. <\/span><\/div>\n<\/div>\n

\"\"<\/p>\n

Now even if we edit the value and set it to say 200002, any further options that you add do not increment automatically to use the next sequence number i.e 200003 but rather would still bring up 200000 as the value by default for every new option that you add hence forth.<\/p>\n

I am not sure if this is a feature or a bug, but I would rather have preferred it remember the last sequence number assigned and increment it from there on.<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

CRM allows you to add\/update\/delete the picklist options of a picklist attribute. However, like most other contact managers that store the text\/reference of the deleted picklist option in the records where it had been used, CRM does not store the reference. It differs in this regard. Once a picklist option has been deleted, all existing\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[19],"tags":[466,1309,1576],"class_list":["post-171","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm","tag-customization","tag-picklist","tag-sequence"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=171"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/171\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}