View Single Post
Old 08-19-2016, 11:46 AM   #139
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Your only option is to wait to synch until I have had a chance to change CALM to allow you to safely synch an Enumeration datatype. The key word is "safely", because the Source Custom Columns of that datatype must be identical in all respects, especially including the list of permitted values, to their respective CALM Target Custom Columns. Otherwise, what happened in CALM just now will happen in your 'real' Source Libraries. So, do not synch those Enumeration datatypes until I can change CALM to do it safely and properly. That will take a couple of days.

In the meantime, you can ensure that all of your matching Enumeration Custom Columns in your Source Libraries are identical in all respects (names, description, and valid values).


DaltonST
DaltonST is offline   Reply With Quote