"Anexar cambios en el texto existente" con los conjuntos de documentos

Question

Estoy tratando de usar el "Anexar cambios en el texto existente" con una biblioteca de documentos que contiene múltiples tipos de contenido basado en documentos.Esta es una forma útil de mantener un comentario en ejecución para el contenido.

Sin embargo, estoy viendo un comportamiento extraño.

He creado mi propia columna de sitio personalizado 'múltiples líneas de texto' y he intentado texto sin formato, texto rico y texto rico mejorado.He seleccionado "sí" para "agregar cambios en el texto existente".El versioning está encendido para la biblioteca de documentos (he intentado configurarlo tanto a la versión mayor como para versiones menores).

Cada vez que edito la columna, el valor se guarda con la marca de fecha / hora, pero solo veo el último valor.Los valores anteriores parecen desaparecer.¿Alguna idea?

Answer 1

The SharePoint "Append Changes to Existing Text" column is a HACK implemented by the SharePoint team, in reality it's just an ordinary text field, but where the rendering is grapping the text from previous versions and using these to create what appears to be a functioning append text field.

So the field is very dependend on the prior versions to exist (you can try deleting a version or an item/document with text on it and see that part disappear from the total text).

Unfortunately versioning hasn't been implemented for folders and because document sets are just glorified folders not for document set either, there is always only the current version (1.0).

This combination things result in "Append Changes to Existing Text" not working with folders and document sets. :-(

Answer 2

I've ran into this before when using "Append-Only" within a Document Library. I've had success in the past using the OOTB Site Column called: Append-Only Comments

This seem to function as expected however I did notice some odd behavior when changing the Display Name of the column. That was in 2007 however. YMMV

Answer 3

I suspect this is linked to the fact that Document Sets don't automatically create versions, I'm assuming that the column is on a Document Set?

Test the behaviour when this column is added to a document content type in the same library.

If the document behaves correctly then roll a custom ItemUpdating event receiver to handle doing the appending.