Hi,
I was wondering if Microsoft is changing standard Option fields into Enum, should we do it also?
In BC25 Could version we have this field:
This is clearly an old field that before was an option and now is an Enum. If I open the sales order, is still option as it was originally.
If I Check Fields table:
OptionMembers = TableFilter,RecordID,OemText,Date,Time,DateFormula,Decimal,Media,MediaSet,Text,Code,Binary,BLOB,Boolean,Integer,OemCode,Option,BigInteger,Duration,GUID,DateTime;
There is No ENUM in this list.
For the breaking change Microsoft says:
This statement is a warning and is related to when you make a new field of type Enum and copy values from Option. As long as Option and Enum have same values, this warning should be no problem. Also, I tried, and changing custom fields from Option to Enum is nor an error or warning for AppSourceCope, also deploying change into Cloud environment the existing values in Option field are not lost.
Still I have this Question: Is it a breaking change if I Replace Option type of field with Enum directly, NOT to create a new Enum field and copy values from Option, that Microsoft says in the above link is a warning.