- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2025 12:20 PM - edited 05-05-2025 12:33 PM
I realized I created a field and its choices in the wrong scope. Tried to change scopes and INSERT (didn't work), so I deleted the field. I recreated the field in the correct scope but when I go to put the choices in, they are being generated in the wrong scope again. I can't delete the choices unless I delete the field, recreate it in the wrong scope, the choices auto-populate but then can be deleted. I go to recreate it a 3rd time in the right scope and the process repeats itself.
I've gone to the choice list table and can't delete the choices from there unless I forego the afore mentioned process for recreating the field in the wrong scope. I've done a background script to nuke the choices but when I go to create them again... they're generating in the wrong scope again. I've tried deleting browser cache too.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2025 04:12 PM
As a work around, I created the field and choices in my PDI and imported the update set. I'd still like to know why this is happening though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2025 10:14 AM
Exactly, that was the intent of this thread, to figure out how to stop the binding.
