October 8, 2013 at 10:06 am
Has anyone successfully used the newest SharePointList Adapters for 2012 at SharePointListAdaptersSetup-Beta-2012-01-28.msi , specifically the Destination connection? I have a working 2008 package, and there, when you edit the SharePointList Destination and click on the Refresh button, the columns on the SharePoint List are imported so that you can then map whichever columns you may want to update.
In this more recent SharePoint Adapter, however, this produces the error shown in the attached screen snippet.
And, since I cannot get the columns, I am unable to update the two that my package should write back to SharePoint.
Incidentally, this beta version of the SharePointList adapters only installs a 32-bit version, and not a 64-bit, so you will find them only in the Program Files (x86) tree.
Any help, comments, suggestions, etc. are greatly appreciated - thanks!
Larry
October 16, 2013 at 2:29 pm
I finally resolved this issue, after weeks of wrangling with it, off and on . . .
A common practice of mine in SSIS is to set the result of a Data Conversion task to the same name as the input, in order to make clear what it represents - see Attachment 1. I believe that in the past (earlier versions of SSIS?), the column mappings tab simply showed the input columns and then "DataConv - ColumnName" or something like that - see Attachment 2.
Much to my surprise, when I looked at the last tab in the SharePoint connector Advanced Editor, there were, in fact, columns with the same name, which is what the System.Linq error was trying to communicate to me! See attachment 3.
After changing the Output Aliases to something different, like "DataConv - SSRS Server Folder," the Refresh button worked just fine, retrieved the metadata from the SharePoint List, and showed the correct columns for mapping.
Whew!!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply