Ideas

Give us your best ideas!

Better handling when field definition changes from non-culture * to multi-culture

Today it is impossible to change field definition without consequences. 

For example:
From non culture to multiculture requires doing manual SQL update on DB. 
Why not have an option when changeing to move all current fields to x language?




  • Artur O
  • Feb 16 2020
  • Future consideration
  • Attach files

Related ideas