Tuesday, August 27, 2013
Friday, August 16, 2013
SSIS and SharePoint List Sources with Lookup Fields
If you are not familiar with the Microsoft SQL Server Community Samples: Integration Services site, then I recommend that you check it out:
https://sqlsrvintegrationsrv.codeplex.com/
The site contains excellent SSIS samples and documentation on how to build solutions for everyday problems using SSIS. One of the most useful samples covers using a SharePoint list as a data source. A special SSIS Data Adapter project has been created and packaged so that you can run an installer and then use SharePoint lists in your SSIS package. The project can be found here:
https://sqlsrvintegrationsrv.codeplex.com/releases/view/17652
After following the installation procedure you end up with a SharePoint List Source and SharePoint List Destination in your toolbox.
You can then use these sources and destinations in any Data Flow Task.
While using the SharePoint List sources today I ran into an issue using a lookup field. Essentially, my package was copying data from a SharePoint list into a local database table. The data exposed by the List Source included the internal SharePoint lookup value. Essentially, it was including the field type and the separator (in this case ‘string;#’), which I did not want in my table.
There is an easy fix to remedy this situation though.
https://sqlsrvintegrationsrv.codeplex.com/
The site contains excellent SSIS samples and documentation on how to build solutions for everyday problems using SSIS. One of the most useful samples covers using a SharePoint list as a data source. A special SSIS Data Adapter project has been created and packaged so that you can run an installer and then use SharePoint lists in your SSIS package. The project can be found here:
https://sqlsrvintegrationsrv.codeplex.com/releases/view/17652
After following the installation procedure you end up with a SharePoint List Source and SharePoint List Destination in your toolbox.
You can then use these sources and destinations in any Data Flow Task.
While using the SharePoint List sources today I ran into an issue using a lookup field. Essentially, my package was copying data from a SharePoint list into a local database table. The data exposed by the List Source included the internal SharePoint lookup value. Essentially, it was including the field type and the separator (in this case ‘string;#’), which I did not want in my table.
There is an easy fix to remedy this situation though.
Thursday, August 8, 2013
SharePoint RenderingTemplate Gotcha!
Recently when working on a SharePoint 2010 project I let a minor mistake cause a great deal of frustration. I was creating a custom field that used a custom rendering template. I have done this before, but I guess on this day my mind was in WebForms land and I ended up with a solution that would deploy, but when I went to access my custom field, it would not render.
Here is a picture of my template… can you see the problem?
I had included the button OnClick call in the control markup. If you do this, your template will not render because it does not know how to wire up that event to it’s respective event handler. Take note of the Control declaration. Unlike normal ASP.Net User Controls, there is no reference to a Code Behind or Inherited Type… therefore… any events that need to be wired up will have to be done in your RenderingTemplateControl class file, and not in the markup!
I hope this helps!
Here is a picture of my template… can you see the problem?
I had included the button OnClick call in the control markup. If you do this, your template will not render because it does not know how to wire up that event to it’s respective event handler. Take note of the Control declaration. Unlike normal ASP.Net User Controls, there is no reference to a Code Behind or Inherited Type… therefore… any events that need to be wired up will have to be done in your RenderingTemplateControl class file, and not in the markup!
I hope this helps!
Friday, August 2, 2013
The Changeling
Today’s society is moving faster than ever, and much like the rapidly evolving technology that we depend on, we ourselves are evolving faster and faster. Not physical evolution mind you, but mental evolution. Our minds are under enormous pressure to adapt, change, and evolve in order to keep pace with the ever-changing landscape that is modern life. Technology is driving this change, and those people who work with technology are most influenced by this “Hyper-evolution”.
The saying:
The saying:
“it’s not what you know, but who you know”…is still true in many ways, but the new world order requires a new saying:
“It’s not what you know, it’s what you can learn”
Subscribe to:
Posts (Atom)