Upload processed documents to SharePoint and set metadata automatically using index fields.
The problem was being caused by the fact that the root site on the server did not grant the users read access.
For example, imagine they are trying to upload to:
The user has full permissions on mysite, but if they try to access http://server/ they get permission denied. Even though the user can upload to mysite, they cannot upload with SimpleIndex because the client objects require permission on the root site.
Granting the users at least read access to the root site at http://server/ resolves the issue.
If a SharePoint user has a Managed Metadata column that they need to set the value for in SimpleIndex, the value they must use is the unique ID for that metadata value, not the value itself.
To find the unique ID, go to a document library that uses the managed metadata column and view the documents in Datasheet view. The unique ID is the part before the semicolon in that column. In the example below, the ERM Classification of “Electric Deal Tickets” has an actual value of “1”.
You will need to have a document with each possible value in order to get all the values this way. If there are a great number of possible values, it is possible to use a script to download them or to pull them directly from the SharePoint database.
SharePoint 2013 & Office365
For SharePoint 2013 and Office365 you need to use the GUID identifier for the taxonomy term.To get the actual value for a managed metadata term, you can use the Unique Identifier that is displayed when you edit the terms in Term Store Management.
In order to get the full list of unique ID values, follow the steps on this here. Use this list to create an autofill table that will replace the text value with the unique ID and map that field to your column in the database.
Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.
To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.
You can also change the user’s default schema on the server to the one matching the table.
A third option is to create a view under the user’s default schema that selects the necessary records.
At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.
Any document processed with SimpleIndex can be uploaded directly to your SharePoint document library, and any custom columns or metadata tags can be set automatically using the SimpleIndex index field values.
Find out more at our SharePoint Document Scanning page.
Integrated custom metadata is only supported in SharePoint 2010 and above, including SharePoint Online / Office 365. Microsoft .NET 3.5 and the SharePoint 2010 Client Object Model are required and must be installed separately in version 7. Version 8 includes a download option in the Global Settings Wizard. Version 8.4 and above include them automatically. Version 7 users can Download the SharePoint 2010 Client Object Model here.
To configure SharePoint export, go to the Advanced Options screen in your Job Options and enter the URL of your document library in the SharePoint Document Library URL setting.
The easiest way to integrate with SimpleIndex is to simply map a network drive to the SharePoint document library and set your Output folder to use this drive. SimpleIndex will create folders and name files automatically using your job settings.
In this configuration, only the Title tag is set. You can also use SimpleIndex‘s file property feature to set EXIF tags (images) or PDF file properties for the Title, Subject, Author and Keywords tags.
One thing to remember when configuring SimpleIndex jobs for SharePoint is the extra restrictions on filenames in SharePoint. For a detailed list please visit SharePoint File Name Restrictions. When using the integrated SharePoint feature with SharePoint 2010 these invalid characters are automatically replaced when exporting.
There are also several inexpensive or free applications that allow you to upload documents processed with SimpleIndex to SharePoint. These can be useful when you have a slow connection and need the files to upload in the background without slowing down production. Here are two of them:
If your SharePoint integration has requirements not met by these solutions, our Professional Services department will be able to design a SharePoint interface to meet your specifications.