Choices keep coming back in wrong scope

TechnologistTim
Tera Expert

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. 

1 ACCEPTED SOLUTION

TechnologistTim
Tera Expert

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. 

View solution in original post

5 REPLIES 5

You-Lan Bribach
Tera Contributor

There are a few things to check:

1. Did you deactivate the field in a scope not your target and those choices come with?

2. Then did you delete all those objects not fitting your needs?

3. You need to create a new field in the scope of your target and choices come with. Please give the new field and choices new names.

 

Thank you.

1. I'm not deactivating it, I'm deleting it. 

2. Everything will be deleted, regardless of scope, when I recreate the field and choices again in the target scope.

3. Problem is, I need those names. 

TechnologistTim
Tera Expert

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. 

First, you should deactivate the field and its choices. Then, remove the relationship of them to delete. If you delelet the field and its choices, when you recreated a new field with the same name (not the label) all those choices will still relate to the field (with the same name) in different scopes. They still bound together with same name and same label. Thank you.