Error Description:
Optionset name is already exist error occur while import solution in CRM
Cause:
The schema name of the source and target environment must be same.
Even though difference in the capitalisation, it won't import schema name must be same(name should be same in the both environment)
Solutions:
There are two solution.
Cons:
If you delete the column in the destination, the data would loss.
"update Attribute set PhysicalName='new_TestData' where name ='new_testdata'"
Cons:
It works only in on-premise
Optionset name is already exist error occur while import solution in CRM
Cause:
The schema name of the source and target environment must be same.
Target system Schema Name | Destination system Schema Name |
---|---|
new_TestData | new_testdata |
Even though difference in the capitalisation, it won't import schema name must be same(name should be same in the both environment)
Solutions:
There are two solution.
- Delete the column name in the destination and import the solution.
Cons:
If you delete the column in the destination, the data would loss.
- Update the attribute table in the destination in the SQL as
"update Attribute set PhysicalName='new_TestData' where name ='new_testdata'"
Cons:
It works only in on-premise
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.