Language Issue?

Jan 30 at 9:43 AM
I use the "staffdocuments" example to copy documents to SharePoint online. Using the powershell I've created the Excel.csv. I converted that .csv to an xlsx. Difs is reading my .xlsx fine but returns an internal server error (500) on every copy. Can this be an language issue? As my SharePoint is Dutch and the .xlsx refers to Englisch fields?

Is not, what other things can be checked?

Thanks, Mike
Coordinator
Jan 30 at 10:04 AM
You need to provide a bit more info

See

https://difs.codeplex.com/wikipage?title=Help%20Using%20DIFS
Jan 30 at 10:26 AM
Edited Jan 30 at 11:15 AM
Sorry ;-)

Difs 2.7.0 (64b)
Logfile enabled according manual but nothing is logged.

Example of xslx row:
FullName
CreationTime
LastWriteTime
Length
Owner   
Author  
Basename    
Name    
Extension   
Action
Data in .xslx
C:\t\20150205 1046 Mail Uit bla.bla@bla.com (MvdH) OSX - LAW FIRM.msg   
25-1-2017 11:02
17-11-2015 12:50
43008   
Domain\bla.bla
<empty>
20150205 1046 Mail Uit bla.bla@bla.com (MvdH) OSX - LAW FIRM
20150205 1046 Mail Uit bla.bla@bla.com (MvdH) OSX - LAW FIRM.msg
.msg
Copy
.XML
<?xml version="1.0" encoding="utf-8"?>
<DataSetImportSettings xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Source>
    <SourceDataSetType>OLEDbSelect</SourceDataSetType>
    <OleDbSourceDataSetSettings>
      <ConnectionString>Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\temp\files.xlsx;Extended Properties="Excel 12.0 Xml;HDR=YES;IMEX=0";</ConnectionString>
    </OleDbSourceDataSetSettings>
    <OleDbTableSourceDataSetSettings />
    <OleDbSelectSourceDataSetSettings>
      <SelectStatement>select * from [files$]</SelectStatement>
    </OleDbSelectSourceDataSetSettings>
    <ODBCSourceDataSetSettings />
    <ODBCSelectSourceDataSetSettings />
    <FileSystemFilesDataSetSettings />
  </Source>
  <Destination>
    <AuthenticationSettings>
      <AuthenticationType>Office365</AuthenticationType>
      <domain />
      <username>bla@bla.nl</username>
      <encryptedpassed></encryptedpassed>
    </AuthenticationSettings>
    <DestinationItemSettings>
      <DestinationItemType>Document</DestinationItemType>
      <ItemExistsBehaviour>Overwrite</ItemExistsBehaviour>
      <ImportMappings>
        <ImportMapping xsi:type="ImportMapping_String">
    
        </ImportMapping>
      </ImportMappings>
    </DestinationItemSettings>
    <DestinationListSettings>
      <DestinationWebUrlRelative>/sites/bla/500-3954858/3608134</DestinationWebUrlRelative>
      <DestinationFolderUrlRelative>/sites/bla/500-3954858/3608134/Gedeelde%20%20documenten%2Fstukken</DestinationFolderUrlRelative>
      <DestinationServerUrl>https://blabla.sharepoint.com</DestinationServerUrl>
      <DestinationListName>Documenten</DestinationListName>
    </DestinationListSettings>
    <DestinationExecutionSettings>
      <PerItemImportThrottle>5</PerItemImportThrottle>
    </DestinationExecutionSettings>
    <SourceColumns>
      <SourceFileNameAndPath>FullName</SourceFileNameAndPath>
      <ContentType>ContentType</ContentType>
      <DestinationSubFolder />
      <DestinationFileName>DestinationFileName</DestinationFileName>
      <Publish>Publish</Publish>
      <CheckInComment>CheckInComment</CheckInComment>
      <PublishComment>Publish</PublishComment>
      <PageLayoutASPXName>PageLayoutASPXName</PageLayoutASPXName>
    </SourceColumns>
  </Destination>
</DataSetImportSettings>
Thanks, again
Coordinator
Jan 30 at 12:13 PM
You have illegal characters in your filenames

e.g. bla@bla I don't think SharePoint will accept.

Try manually uploading a file like that to SP to see

Also you have empty import mapping
    <ImportMapping xsi:type="ImportMapping_String">

    </ImportMapping>
Jan 30 at 12:22 PM
I can upload manually.
But i think it will be the mapping.

I'll have to map the Englisch propertyname (in excel) to the Dutch doc library field, I guess?

Thanks, Mike
Jan 30 at 12:50 PM
I thought the filename in Sharepoint would be the "Name" in the Excel sheet, so I left DestinationFileName empty..... ahum.
Changing that did solve the error.

Thanks for your help and the great tool!!!