First, SPServices is a very helpful tool, and Thanks! for providing it to the SharePoint community!!!
We have a list within SP2010 to track field issues which has various columns including 'Status' (pick from choices) and 'Comments' (multi-line entry with "Append Changes to Existing Text" enabled). We have reporting requirements external
to SP to track the amount of time an issue has been in various 'Status' states.
We are running a SPServices script which checks each issue for 'Status' changes using GetVersionCollection. If there has been a 'Status' change, the list of each change with date for the issue is rebuilt as a string, and the updated string is stored
in a 'Status History' column for the issue using UpdateListItems for later use by the external reporting.
The undesired behavior we see is that the last update to the 'Comments' column is duplicated when a 'Status History' change is updated. This behavior has been reported before in this forum:
and apparently by other users/applications:
We are looking for a way to avoid these duplicate entries in the 'Comments' column. The next approach we will try is to disable "Append Changes to Existing Text" in the 'Comments' column before running the script, and then reenabling it afterwards.
Questions for the community are:
1) Has anyone been able to workaround the duplicate entries issue?
2) If disabling the "Append Changes to Existing Text" in the 'Comments' column works, is there a way to also automate this disabling and reenabling in a SPServices script?