We have installed managed solutions into system test environment and then run the data import process by the business provided sheets which were converted to csv.
After a while business requested that one of the option is not triggering the functionality when looking at the option, that option wasn't even provided by us i.e. from dev environment. but it does exists in the system test and other environments.
After spending quite a bit of time, I figured it out the option was added due to business provided that option in the data import sheet, and actually that option wasn't specified with in the FSD and we didn't implement any logic against that option.
When data import is done for the optionset value CRM maps the value if the optionset value exists if it doesn't exists then CRM CREATES THE OPTIONSET VALUE AUTOMATICALLY, where I was expecting the records to fail.
Now I know what the reason is we explained the business what has happened and we need to work on to update customization i.e. javascript/plugin to consider the new value as well.
After a while business requested that one of the option is not triggering the functionality when looking at the option, that option wasn't even provided by us i.e. from dev environment. but it does exists in the system test and other environments.
After spending quite a bit of time, I figured it out the option was added due to business provided that option in the data import sheet, and actually that option wasn't specified with in the FSD and we didn't implement any logic against that option.
When data import is done for the optionset value CRM maps the value if the optionset value exists if it doesn't exists then CRM CREATES THE OPTIONSET VALUE AUTOMATICALLY, where I was expecting the records to fail.
Now I know what the reason is we explained the business what has happened and we need to work on to update customization i.e. javascript/plugin to consider the new value as well.
