Paul Liebrand's Weblog

Welcome to my blog mainly about SharePoint

Skip to: Content | Sidebar | Footer

Google Search

Adobe Acrobat X and SharePoint – close, but no cigar

17 May, 2011 (17:18) | SharePoint, Tools | By: Liebrand

Adobe X was released at the end of last year and one of the feature points announced was “Native, seamless integration with Microsoft SharePoint”.  On the surface, everything appears to work correctly and solved one of the main issues with Adobe Acrobat with SharePoint I blogged about in the past.

Recently discovered that it is not as seamless as we would like. Adobe X does not appear to work with the following column types:

  • Date and Time
  • Person or Group
  • Lookup

If you have a date and time column on a document library and you attempt to save the PDF back to SharePoint, you will receive the following error message:

File check in failed. The server said:

“Invalid date/time value

A date/time field contains invalid data. Please check the value and try again.”


Using Fiddler, I can see the SOAP request that the date field is being sent over as straight text. When using the lists web service, it requires the date to be in ISO 8601.

<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:xsd="" xmlns:xsi="">
    <UpdateListItems xmlns="">
            <Batch OnError="Continue">
                <Method Cmd="Update" ID="1"><Field Name="Title"/>
                    <Field Name="Date">05/17/2011 05:00:00</Field>
                    <Field Name="FileRef"></Field>
                    <Field Name="ID">1</Field>
                    <Field Name="ContentTypeId">0x010100EAB6ED7FBD4A0042A6F9326944DCEE19</Field>
                    <Field Name="ContentType">Document</Field>

The Person or Group field just shows the value as it stored within SharePoint:


The Lookup field just does not show anything.

I hope Adobe is listening and releases an update that resolves these issues.


We received word from Adobe that the “date” issue will be resolved in a release slated for September.  The other issues will be hopefully resolved in the version after that (next year).

Post to Twitter Post to Delicious Post to Digg Post to Facebook Post to Reddit