Hi I am trying to use the Odata connection manager to SharePoint
I keep getting the following
Need to to change DTDprocessing property on XMLreader settings to parse...
Where can this be done please ?
Just want to link to table in share point
Please help
Related
as title says I am trying to read the Excel file placed on online SharePoint using the OData component in SSIS.
I am trying to make an SSIS package that will update my database in sql server with the data from that Excel file. I managed to do that when my file is placed locally.
I also managed to see my file using by adding /_vti_bin/listdata.svc/ inside target URI, i get an Share Point list where one of the components is my excel file, but I can't open it that way.
Also I need to use credentials to access the SharePoint.
I would be thankfull for any help :D
Acceptable solution would be to download that file first, but I haven't managed to do that either.
I made connection with Share Point with oData Source. After that I got Collection and Under collection excel files are placed.
How to download excel file from Collection ?
Have you tried any options yourself? Please go through this link first to understand how should you be asking questions -How To Ask
HTTP Connection Manager and a script task should do the job. There are some custom components on codeplex to download the sharepoint lists (unless they are https connections) using SSIS.
SSIS Sharepoint Connection using OData connector. I was able to connect to Sharepoint site fine and was able to see the data thru preview and all.. but when i execute the task i get below error.
[OData Source [2]] Error: The OData Source was unable to process the data. Object reference not set to an instance of an object.
Task: OData as Source(with SP connection information) and OLE DB Destination.
I worked with this SharePoint connector a couple of years ago and recall it being somewhat tricky to set up. Check the following link to see if you may have left out any steps.
http://dataqueen.unlimitedviz.com/2011/06/how-to-use-a-sharepoint-list-as-a-data-source-in-your-ssis-package/
Also, I remember that by default the SharePoint connector mapped every column, most of which were not needed. This resulted in a memory limitation and was resolved by removing the mappings not needed.
I am trying to make modifications to a named query in a cube and the data source view (.dsv) won't allow me to make edits or create a new named query. It gives me a login error even though I can successfully do a test connection in the data source dialog and can login successfully with SSMS.
The error is: "Login failed for user "
If I instead use the Windows authentication I am able to do everything; however, I would like to use the SQL Server Authentication option.
Are there privileges that need to be set for this? I'm pretty sure I've tried giving this user everything from db_owner etc in my local environment and still no luck.
I was wondering if maybe SSAS requires a specific role to allow SQL Server Authentication to be used for editing/creating named queries in the data source view.
Please refer to the following steps to slove this issue:
In the SSDT development interface, double-click on your data source.
In the Data Source Desginer dialog, please click "Edit".
Please select "SqlClient Data Provider", and then use your SQL Account for the data source.
Follow this link
(https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b5f05388-42e0-4fb6-92a9-d7d3e08aa98c/ssdt-2012-named-query-problem?forum=sqlanalysisservices)
On the main page home.aspx, I would like to query some data from Oracle database.
I've carefully looked for a such option, but I cannot find anything releated to it.
Can someone please guide me?
Thank you.
Install the Oracle connector and register it as safe in the web.config of the SharePoint Web. Use it like any other sql connector but with OracleConnection as you should.
I myself would have chosen a bit different approach and developed a webpart instead. If you develop and deploy a webpart project in SharePoint 2010 any used modules should be properly registered automatically during the deployment. Start with webparts here, http://msdn.microsoft.com/en-us/sharepoint/ee513148.aspx
And if you don't know what the above means you probably shouldn't mess with SharePoint that way! (Sorry but it's true)