Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[michel]

I have a MC12 library configured with some custom fields. One of them is a field STYLE which is a list (semi-comma delimited). Of course I have thousand of files tagged with these custom fields including STYLE.

MC13 added a new "non-custom" field named STYLE which is a string. So I have to migrate all my files moving styles to a new custom field (SUB-GENRE) which is a list.

But, who knows, may be MC14 will add a new "non-custom" field named SUB-GENRE and I will need to migrate again...

It seems that there is a problem somewhere, no ? Setting custom fields expose you to have to migrate your library and yours files each time a new version of MC is released and to use another (and probably less good) name for custom fields.

Is it really impossible to "unlock" the format of STYLE ?