Unum inceptis nunc facit usum de tractanda Metadata columnas.
Sunt plura in opere incepto unus creavit progressum multum (dulcis) test notitia. Ego voluit de quod actio, habuitque et reddidit mihi in nibh lectus. Qui habebat tristis effectus disabling curo totus of meus site metadata columnis quocumque editform.aspx aut vere aut paginae libellorum, usquam, ut ostensum:
Instaurati notitia ostendit valores, sed non erant vero eos. Interestingly, Quaero rutrum poteram scriberem aliquid ex agris elit. Duis non modo ex eis quemquam. Non etiam creare nova prorsus in illis columnis pages / list items. Erroresque et non inveni in ligno dolor.
I played around with it for longer than I like to admit until somewhere along the idea I got the idea to update the site column in the web UI. My thought was that maybe the backup/restore process broke some connections between the MMS service and the site columns. That did, in facto, solve it. It’s a pain because you have first select the right term group and second, fix it everywhere it’s used. In meam, it’s worth the effort to get that sweet, sweet test data.
It does beg the question – how do you keep a test environment in good shape that’s a backup of production? I think that’s my root cause here and it’s a kind of normal thing for people to create a test environment as a backup of production… Questions, questions..
</finem>
Sequi me in Twitter ad http://www.twitter.com/pagalvin
This is a common scenario and it happened to me right now. Thanks for reminding me of updating the field. 😉