SharePoint API or SharePoint Web services?
Posted on 2010-08-17
I have developed an application that parses a text file and uses that data to populate a SharePoint List (add & update) as well as attach any files that may be listed in the text file to its corresponding List Item. I am using the SharePoint API at this point - not the SharePoint Web services.
The issue is permissions. In order to accomplish this I have had to grant the account that this application runs under an extraordinary level of permissions (for example the account had to be set as SA on the SqlServer that the databases reside on for the Content, Config, and Admin databases that this SharePoint site uses).
Obviously this is unacceptable in a production environment - and it is now time to move this application to production.
I'd like to know if there are any ways to get around having to grant such privileges to the account that this app runs under, and/or if I should modify the application to use the SharePoint Web services in place of the API.
I chose to use the SharePoint API due to the limiting number of updates that can be made during a batch (160). I can break up my import to work in chunks of say 100 and add list items that way, but I am also concerned about performance if the import were have to import 300 list items and attach 900 3Mb files to that batch 300 List Items(3 per List Item).
Can any/all SharePoint Development experts please offer some advice?
Thank you VERY much for your assistance.