there is nothing you must do, as the field is nullable.
There isn’t really a scripted upgrade path, since the field is unique and max 50 char. However you can try this SQL:
update dataelementcategoryoption set name = substring(name,0,50);
In 2.17 we have a new option for display either name or short name in analysis apps, and hence it could be good to set this.
On Wed, Nov 19, 2014 at 5:10 AM, Mahendra Kariya email@example.com wrote:
We just noticed that a new mandatory field ‘shortName’ has been added to category options.
We were just wondering about the migration strategy for the data which is already in prod without the short name. Do we need to do something about it or DHIS will take care of this scenario internally?