Monthly Archives: July 2011

Start the Organization Browser at any Account Name

Posted on July 29, 2011 by Adam Preston

I’m a huge fan of the SharePoint 2010 Organization Browser, the Silverlight web part that displays the company hierarchy based off of the Active Directory Manager field. However, my biggest complaint was that there was no way to set the default user – meaning I want when the page loads for the focused user to be say a CEO or Department Head instead of me. The easiest solution would be to promote me to CEO, but that didn’t fly to well in the office. So, I had to turn elsewhere.  
Read more...

Posted in Administration | Tagged | 21 Comments

Set a Service Application Administrator in SharePoint 2010

Posted on July 28, 2011 by Adam Preston

SharePoint 2010 allows Farm Administrators the ability to delegate administrators for individual Service Applications. Once provisioned, the Service Application Administrator will gain access to a security-trimmed Central Administration where they can only access and configure the roles granted to them. This is perfect for scenarios when perhaps you want to offload the Profile, Managed Metadata, or Search features off onto other departments.  
Read more...

Posted in Administration | Tagged , | 1 Comment

Fixing Telerik error: “Microsoft JScript runtime error: Object doesn’t support this property or method”

Posted on July 5, 2011 by Brian Foote

I ran into this issue upgrading a site to use Telerik’s MVC controls. Once I added all the Telerik includes I would get the ‘Microsoft JScript runtime error: Object doesn’t support this property or method’ error on every page. Only happened in IE 8 though. After some troubleshooting I deduced the following line was throwing the error:  
Read more...

Posted in .Net, JQuery, MVC, Telerik | Tagged , , | Leave a comment

Use Task Name as Stored Procedure Argument in SSIS

Posted on July 5, 2011 by Kevin Carter

This is something that probably doesn’t come up that often, but I had a situation recently where a routine was called repetitively. The client didn’t want a For/Loop type of solution, they wanted to manage it in the package, so I created the stored procedure to execute the routine and it accepted the name of the task from the SSIS package as an argument to direct the function. Doing it this way, meant the client only had to copy the task and rename it to change its function. They did not have to edit the internal call for the task.  
Read more...

Posted in Business Intelligence, SQL | Leave a comment