Issue during changing type from Duration type to choice type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2025 11:47 AM
I had to change the type for one field from duration to choice .We can not change directly the type from duration to choice .So i created one temporary field and stored existing data in that field .
Then created a new update set.
After that i deleted the current duration field and added new field with choice type with same column name which i had for duration to avoid other related issues. I was able to do this in lower instance but when i am moving update set , I am getting error like type conversion is not allowed from duration to choice for this column name. What should i do now . Please help ,do i need to move deletion in separate update set if yes then how should i capture deletion now in lower instance (moving the changes from DEV TO TEST ,i have duration field available in STAGE and PROD now).When checking the versions in DEV for newly created choice type field dictionary (previously i had same column name duration field), I can see deletion is captured and on same field insert/update is captured and type changed. Please suggest me the way to rectify the error in update set in TEST instance also how can fix and move the newly created field in TEST and remove duration field in TEST.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2025 02:22 PM
You can avoid the restore of the instance. Capture the field deletion in an update set, separately from it being recreated. Do this now and Complete that and promote. Now Assuming you have an existing update set that creates the field as desired, promote that. And for a Preview problem with that one update, select "Accept remote update" ( as that is the one you want) and commit. Verify the field is as desired. Then in the same sequence, promote and commit both update sets in the next instance. When you clone over the source instance (dev) all will be ok there. In the meantime, recreate the field as desired in dev. but don't capture that in an update set other than Default for Global scope.