Have you used D365 make.powerapps.com to create a new option set field?
If you have you may (or may not) have noticed that there is a bit of a change. When you click you create a new field (that’s an option set) there is a small difference in the fact you can create a new option set, use and existing but can’t put your list embedded into the field.
Personally I don’t think this is a bad change as I have spent years creating new fields with global option sets, writing workflows and mapping old embedded option set values over to new fields with e global option set. However, what does this mean with existing embedded fields?
If you open a existing field you will see that there is now an option set called ‘local option set’
If you click on the edit option set button you will see all the values and will be able to manage the list to put in more / amend
So in summary, if you currently have an embed option set nothing will be lost but, building something new you need to build a global set.