Archives

Javascript event handling and dynamic lists in SharePoint

by Gustaf Westerlund | Aug 22, 2007

As many of you already know and probably have used, it is possible using javascript to create dynamic drop-down-lists. For instance one drop-down list that selects country and another that lets you select a city in that country. Depending on which country you select, you want the options in the city drop-down to change.

This is a quite common task in MS CRM where javascript is a common tool. In SharePoint however, javascript isn’t as common. I am currently working with a colleague of mine, Sebastian Tegel, at a large swedish customer of ours. They had this requirement on some metadata in a SharePoint library so Sebastian and I used the same principles as I usually use in MS CRM to create dynamic drop-down lists in SharePoint. Sebastian has a very nice and instructive posting on his blog on how this is done. Please have a look at it: http://sebastiant.blog.com/2023682/

In the posting before that, he also describes how to create your own custom edit form for a document properties page. This is very useful in these cases, so please have a look at that as well. (http://sebastiant.blog.com//custom+forms/).

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Not so simple SharePoint and CRM integration

by Gustaf Westerlund | Aug 21, 2007

A customer of mine wanted to integrate their MOSS Ent with CRM 3. Specifically they wanted to be able to handle documents in CRM with SharePoint, not surprising since the document handling in MS CRM 3 is bad, if you are a bit positive. They were running 2 servers, one with CRM and one with MOSS Ent. Both with their own SQL 2005 installations (to avoid problems with SPN:s and such).

The solution? I based the solution on my previous posting from October 2006 where I described how to do this; Simple SharePoint and CRM integration (http://gustafwesterlund.blogspot.com/2006/10/simple-crm-and-sharepoint-integration.html). That was WSS 2 and both applications were running on the same server. So, not really the same setup, but, I felt, it shouldn’t be a problem.

My plan was to create a SharePoint site using a specific custom template on the Account PostCreate callout. The callout would set the websiteurl attribute and an onLoad javascript would show a custom aspx-page that shows a documents webpart using the minimal.master (in order to hide all the SharePoint specific framing).

I started off by creating the PostCreate callout. Not a problem, just create a normal class file with the following content:

using System;

using Microsoft.Crm.Callout;

using Callouts.CRMSDK;

namespace Callouts

{

///
<summary>

/// Summary description for Class1.

///
</summary>

public
class Account: CrmCalloutBase

{

public Account()

{

}

public
override
void PostCreate(CalloutUserContext userContext, CalloutEntityContext entityContext, string postImageEntityXml)

{

CrmService service = new CrmService();

service.Credentials = System.Net.CredentialCache.DefaultCredentials;

service.CallerIdValue = new CallerId();

service.CallerIdValue.CallerGuid = userContext.UserId;

systemuser user = (systemuser)service.Retrieve(EntityName.systemuser.ToString(), userContext.UserId, new AllColumns());

account acc = (account)service.Retrieve(EntityName.account.ToString(), entityContext.InstanceId, new AllColumns());

// Code to create sharepoint site/subweb and set acc.websiteurl to the url.

service.Update(acc);

}

And add a web reference to the CRM webservice (look in the SDK to find the exact URL). As you probably can see, I called it CRMSDK (strange name actually, but it´s tradition).

And the callout.config.xml looked like this:

<callout.config
version=“3.0“
xmlns=“http://schemas.microsoft.com/crm/2006/callout/“>

</callout>

</callout.config>

Well, I modified the code and set some attribute of the account to something just to make sure it worked. It did.

How to create a site in SharePoint from one server? Well, first I tried adding Microsoft.SharePoint.dll which contains lots of nice stuff to access the SharePoint data. This was the technique I had used previously and thought it might be good this time too. But no, it can actually only be used on the same server as SharePoint and not on some other server.

There are still a lot of nice web services in SharePoint, I could probably find some web method that would let me create my site. I started by looking in the WssSDK…

But I could find anything useful. The natural webservice would of course be webs.asmx and it contains lot of nice functions to handle SharePoint webs, like GetWeb() and so on. But I found no way of creating a new site. In the admin.asmx I found a method called createSite() but that creates sitecollections which is not really what I wanted. (Each sitecollection has unique security handling, template and sitedefinition setup and a lot of other specific stuff) My customer has around 5000 customer and I would want to create 5000 sitecollections.

I started searching the Internet. But, no. All I could find was a blog entry by Nick Swan describing how to use admin.createSite() (http://weblog.vb-tech.com/nick/archive/2006/03/07/1472.aspx).

I contacted Pontus Haglund and Kalle Becker at Microsoft and my colleague Sebastian Tegel and asked them if they knew how to do this or could assist in any way. They didn’t unfortunately.

I was left with only one major option as I saw it; creating my own web service that used Microsoft.SharePoint.dll functions to create the web site (subweb). I had found a blog that described how to do this (http://blogs.ittoolbox.com/km/sharepoint/archives/creating-a-custom-web-service-for-sharepoint-13553). So, I thought that it shouldn’t be that big of a hazel. To make sure my SharePointcode worked, I first created a normal windows forms application that created a site according to certain variables. I found that the following code worked very well:

string url = “”;

SPSecurity.RunWithElevatedPrivileges(delegate()

{

SPSite siteCollection = new SPSite(“http://intranet”);

SPWebCollection subSites = siteCollection.AllWebs[“customersites”].Webs;

SPWebTemplateCollection templates = siteCollection.GetCustomWebTemplates(1033);

SPWebTemplate template = templates[0];

SPWeb mySite = subSites.Add(name, Title, Description, 1033, template, false, false);

mySite.Update();

url = mySite.Url;

});

return url;

After a suggestion from my colleague Sebastian Tegel, I ran all the code with Elevated Privileges. Not sure it is actually needed but I added it to make sure that there isn’t any security issues with the current user and permissions to create sites.

Now, I just had to follow the blog I had found. Again my misfortune struck me, as I was unable to make any sense of it. I got the web service to work as long as I didn’t use any SharePoint functions. When I did, I got the following error:

System.IO.FileNotFoundException: The Web application at http://intranet could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)

.

I was using the exact same code as I had tested in the forms test application so there wasn’t any problems there.

The blog post mentions a lot about strong naming assemblies but it doesn’t reference it with the strong name and my experience told me that this error probably was due to Code Access Security (CAS) problems. The assembly should be strong-named, placed in the GAC and referenced using the strong name.

I think some important pictures has fallen out of the blog why it doesn’t make much sense. It did however mention that there was a walk-through on msdn that described the same thing. This was my next lead on the way to my goal of SharePoint document handling In MS CRM 3.

I found the walk-through (http://msdn2.microsoft.com/en-us/library/ms464040.aspx) and followed it minutely. It gave me a lot better feeling than the first blog posting I had found. In short, it described how to create a web service asmx-file that references a strong named assembly with a class of web methods in it. When created, the program disco.exe was used to create wsdl and disco files for the web service. When these had been created, the were renamed to become aspx files so that they can dynamically link to the webservice depending on where in SharePoint it has been referenced. (all sharepoint webservices can be found in the sub directory of /_vti_bin/ of any site, for instance the web service webs.asmx can be found in both the url http://intranet/_vti_bin/webs.asmx and http://intranet/customersites/webs.asmx). When the wsdl and disco files have been properly modified to fit the SharePoint standard of handling this feature, the new web service has to be added to the file spdisco.aspx which is a directory of all web services that are available.

After a lot of hazel, I got this to work, and with a strong named assembly, deployed in the GAC and run in the SharePoint context. I finally got it to work the way I wanted it to.

So, if you also want your own web service in SharePoint. I would suggest following the walk-through very thoroughly and I have a few pointers. My web service was called WebsExtra.asmx, my class was called Service, and the assembly “WSTools.dll”.

First, make sure the asmx-file works. Develop it using a normal web application. You should be able to address it. I had created a new web site using TCP port 8000 and hence tried: http://intranet:8000/WebsExtra.asmx. If that doesn’t work, make sure you have strong named your assembly correctly, deployed it the the GAC (i.e. copied it to c:windowsassembly) and addressed the class using the full strong name (“Service, WSTools, Version=1.0.0.0, Culture=Neutral, PublicKeyToken=037c5a828198ba1e” in my case).
Ok. That works. Good. Make sure the file also works when you placed it in the _layouts directory according to the walk-through. If not, you might still not be addressing the class with the full strong name.
After I created the files WebsExtra.wsdl and WebsExtra.disco, copied them to the ISAPI directory, renamed them to WebsExtrawsdl.aspx and WebsExtradisco.aspx, and modified them to be able to handle the dynamic linking that SharePoint uses, I made sure that I could really see the aspx-files using IE. I found them at http://intranet/_vti_bin/WebsExtrawsdl.aspx and http://intranet/_vti_bin/WebsExtradisco.aspx .
Also check the contents of them and make sure they follow the same structure as similar files in the ISAPI directory (for instance Webswsdl.aspx and Websdisco.aspx, which you also can find using IE). Make sure that the referencing to the web service really uses the name you have set and not the name used in the walk-through.At the bottom of this entry is a copy of the files I used and a copy of the result I got in IE.
When both these files work, make the additions to the bottom of spdisco.aspx as well (within the discovery-tag though). This file can also be found using IE. You can probably guess it’s url. Have a look at my version at the bottom of this entry, including the result in IE.
When I got that working, I now tried to access the addresses:
http://intranet/_vti_bin/WebsExtra.asmx?wsdl and http://intranet/_vti_bin/WebsExtra.disco. These aren’t actually files that you can find in the ISAPI directory but are mapped to the aspx-files mentioned in 3 above. You can check this by checking one of the out-of-the-box web services like Webs.asmx.
When you’ve got all these working properly, you should be able to add the web service as a web reference in some test project. (I usually use Windows Forms programs since they are the easiest to debug). If all has been set up properly, you should now be able to add the web service as a web refence. If the dialog gives you problems, it is usually due to errors in the wsdl or disco files. I had lots of these and was quite close to suicide but finally found them all. Most of the problems I had were due to the fact that I had used Visual Studio to edit the wsdl and disco aspx files. VS 2005 had been very “helpful” and had added =”” here and there, making the syntax erroneous. So, my suggestion, use notepad to copy paste the code from the walk-through. When that is done, you can use VS 2005 to modify the code.

WebsExtrawsdl.aspx

<%@
Page
Language=”C#”
Inherits=”System.Web.UI.Page”
%>

<%@
Assembly
Name=”Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
%>

<%@
Import
Namespace=”Microsoft.SharePoint.Utilities”
%>

<%@
Import
Namespace=”Microsoft.SharePoint”
%>

<% Response.ContentType = “text/xml”; %>

<wsdl:definitions
xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/”
xmlns:tm=”http://microsoft.com/wsdl/mime/textMatching/”
xmlns:soapenc=”http://schemas.xmlsoap.org/soap/encoding/”
xmlns:mime=”http://schemas.xmlsoap.org/wsdl/mime/”
xmlns:tns=”http://tempuri.org/”
xmlns:s=”http://www.w3.org/2001/XMLSchema”
xmlns:soap12=”http://schemas.xmlsoap.org/wsdl/soap12/”
xmlns:http=”http://schemas.xmlsoap.org/wsdl/http/”
targetNamespace=”http://tempuri.org/”
xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/”>

<wsdl:types>

<s:schema
elementFormDefault=”qualified”
targetNamespace=”http://tempuri.org/”>

<s:element
name=”CreateSharePointSubWeb”>

<s:complexType>

<s:sequence>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”portalUrl”
type=”s:string”
/>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”subsite”
type=”s:string”
/>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”name”
type=”s:string”
/>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”Title”
type=”s:string”
/>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”Description”
type=”s:string”
/>

<s:element
minOccurs=”1″
maxOccurs=”1″
name=”templateId”
type=”s:int”
/>

</s:sequence>

</s:complexType>

</s:element>

<s:element
name=”CreateSharePointSubWebResponse”>

<s:complexType>

<s:sequence>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”CreateSharePointSubWebResult”
type=”s:string”
/>

</s:sequence>

</s:complexType>

</s:element>

<s:element
name=”HelloWorld”>

<s:complexType
/>

</s:element>

<s:element
name=”HelloWorldResponse”>

<s:complexType>

<s:sequence>

<s:element
minOccurs=”0″
maxOccurs=”1″
name=”HelloWorldResult”
type=”s:string”
/>

</s:sequence>

</s:complexType>

</s:element>

</s:schema>

</wsdl:types>

<wsdl:message
name=”CreateSharePointSubWebSoapIn”>

<wsdl:part
name=”parameters”
element=”tns:CreateSharePointSubWeb”
/>

</wsdl:message>

<wsdl:message
name=”CreateSharePointSubWebSoapOut”>

<wsdl:part
name=”parameters”
element=”tns:CreateSharePointSubWebResponse”
/>

</wsdl:message>

<wsdl:message
name=”HelloWorldSoapIn”>

<wsdl:part
name=”parameters”
element=”tns:HelloWorld”
/>

</wsdl:message>

<wsdl:message
name=”HelloWorldSoapOut”>

<wsdl:part
name=”parameters”
element=”tns:HelloWorldResponse”
/>

</wsdl:message>

<wsdl:portType
name=”ServiceSoap”>

<wsdl:operation
name=”CreateSharePointSubWeb”>

<wsdl:input
message=”tns:CreateSharePointSubWebSoapIn”
/>

<wsdl:output
message=”tns:CreateSharePointSubWebSoapOut”
/>

</wsdl:operation>

<wsdl:operation
name=”HelloWorld”>

<wsdl:input
message=”tns:HelloWorldSoapIn”
/>

<wsdl:output
message=”tns:HelloWorldSoapOut”
/>

</wsdl:operation>

</wsdl:portType>

<wsdl:binding
name=”ServiceSoap”
type=”tns:ServiceSoap”>

<soap:binding
transport=”http://schemas.xmlsoap.org/soap/http”
/>

<wsdl:operation
name=”CreateSharePointSubWeb”>

<soap:operation
soapAction=”http://tempuri.org/CreateSharePointSubWeb”
style=”document”
/>

<wsdl:input>

<soap:body
use=”literal”
/>

</wsdl:input>

<wsdl:output>

<soap:body
use=”literal”
/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation
name=”HelloWorld”>

<soap:operation
soapAction=”http://tempuri.org/HelloWorld”
style=”document”
/>

<wsdl:input>

<soap:body
use=”literal”
/>

</wsdl:input>

<wsdl:output>

<soap:body
use=”literal”
/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:binding
name=”ServiceSoap12″
type=”tns:ServiceSoap”>

<soap12:binding
transport=”http://schemas.xmlsoap.org/soap/http”
/>

<wsdl:operation
name=”CreateSharePointSubWeb”>

<soap12:operation
soapAction=”http://tempuri.org/CreateSharePointSubWeb”
style=”document”
/>

<wsdl:input>

<soap12:body
use=”literal”
/>

</wsdl:input>

<wsdl:output>

<soap12:body
use=”literal”
/>

</wsdl:output>

</wsdl:operation>

<wsdl:operation
name=”HelloWorld”>

<soap12:operation
soapAction=”http://tempuri.org/HelloWorld”
style=”document”
/>

<wsdl:input>

<soap12:body
use=”literal”
/>

</wsdl:input>

<wsdl:output>

<soap12:body
use=”literal”
/>

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service
name=”Service”>

<wsdl:port
name=”ServiceSoap”
binding=”tns:ServiceSoap”>

<soap:address
location=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
/>

</wsdl:port>

<wsdl:port
name=”ServiceSoap12″
binding=”tns:ServiceSoap12″>

<soap12:address
location=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
/>

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

When accessed at http://intranet/_vti_bin/WebsExtrawsdl.aspx or http://intranet/_vti_bin/WebsExtra.asmx?wsdl the following was the result:

<wsdl:definitions
xmlns:soap=“http://schemas.xmlsoap.org/wsdl/soap/“
xmlns:tm=“http://microsoft.com/wsdl/mime/textMatching/“
xmlns:soapenc=“http://schemas.xmlsoap.org/soap/encoding/“
xmlns:mime=“http://schemas.xmlsoap.org/wsdl/mime/“
xmlns:tns=“http://tempuri.org/“
xmlns:s=“http://www.w3.org/2001/XMLSchema“
xmlns:soap12=“http://schemas.xmlsoap.org/wsdl/soap12/“
xmlns:http=“http://schemas.xmlsoap.org/wsdl/http/“
targetNamespace=“http://tempuri.org/“
xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/“>

<wsdl:types>

<s:schema
elementFormDefault=“qualified“
targetNamespace=“http://tempuri.org/“>

<s:element
name=“CreateSharePointSubWeb“>

<s:complexType>

<s:sequence>

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“portalUrl“
type=“s:string“ />

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“subsite“
type=“s:string“ />

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“name“
type=“s:string“ />

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“Title“
type=“s:string“ />

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“Description“
type=“s:string“ />

<s:element
minOccurs=“1“
maxOccurs=“1“
name=“templateId“
type=“s:int“ />

</s:sequence>

</s:complexType>

</s:element>

<s:element
name=“CreateSharePointSubWebResponse“>

<s:complexType>

<s:sequence>

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“CreateSharePointSubWebResult“
type=“s:string“ />

</s:sequence>

</s:complexType>

</s:element>

<s:element
name=“HelloWorld“>

<s:complexType />

</s:element>

<s:element
name=“HelloWorldResponse“>

<s:complexType>

<s:sequence>

<s:element
minOccurs=“0“
maxOccurs=“1“
name=“HelloWorldResult“
type=“s:string“ />

</s:sequence>

</s:complexType>

</s:element>

</s:schema>

</wsdl:types>

<wsdl:message
name=“CreateSharePointSubWebSoapIn“>

<wsdl:part
name=“parameters“
element=“tns:CreateSharePointSubWeb“ />

</wsdl:message>

<wsdl:message
name=“CreateSharePointSubWebSoapOut“>

<wsdl:part
name=“parameters“
element=“tns:CreateSharePointSubWebResponse“ />

</wsdl:message>

<wsdl:message
name=“HelloWorldSoapIn“>

<wsdl:part
name=“parameters“
element=“tns:HelloWorld“ />

</wsdl:message>

<wsdl:message
name=“HelloWorldSoapOut“>

<wsdl:part
name=“parameters“
element=“tns:HelloWorldResponse“ />

</wsdl:message>

<wsdl:portType
name=“ServiceSoap“>

<wsdl:operation
name=“CreateSharePointSubWeb“>

<wsdl:input
message=“tns:CreateSharePointSubWebSoapIn“ />

<wsdl:output
message=“tns:CreateSharePointSubWebSoapOut“ />

</wsdl:operation>

<wsdl:operation
name=“HelloWorld“>

<wsdl:input
message=“tns:HelloWorldSoapIn“ />

<wsdl:output
message=“tns:HelloWorldSoapOut“ />

</wsdl:operation>

</wsdl:portType>

<wsdl:binding
name=“ServiceSoap“
type=“tns:ServiceSoap“>

<soap:binding
transport=“http://schemas.xmlsoap.org/soap/http“ />

<wsdl:operation
name=“CreateSharePointSubWeb“>

<soap:operation
soapAction=“http://tempuri.org/CreateSharePointSubWeb“
style=“document“ />

<wsdl:input>

<soap:body
use=“literal“ />

</wsdl:input>

<wsdl:output>

<soap:body
use=“literal“ />

</wsdl:output>

</wsdl:operation>

<wsdl:operation
name=“HelloWorld“>

<soap:operation
soapAction=“http://tempuri.org/HelloWorld“
style=“document“ />

<wsdl:input>

<soap:body
use=“literal“ />

</wsdl:input>

<wsdl:output>

<soap:body
use=“literal“ />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:binding
name=“ServiceSoap12“
type=“tns:ServiceSoap“>

<soap12:binding
transport=“http://schemas.xmlsoap.org/soap/http“ />

<wsdl:operation
name=“CreateSharePointSubWeb“>

<soap12:operation
soapAction=“http://tempuri.org/CreateSharePointSubWeb“
style=“document“ />

<wsdl:input>

<soap12:body
use=“literal“ />

</wsdl:input>

<wsdl:output>

<soap12:body
use=“literal“ />

</wsdl:output>

</wsdl:operation>

<wsdl:operation
name=“HelloWorld“>

<soap12:operation
soapAction=“http://tempuri.org/HelloWorld“
style=“document“ />

<wsdl:input>

<soap12:body
use=“literal“ />

</wsdl:input>

<wsdl:output>

<soap12:body
use=“literal“ />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

<wsdl:service
name=“Service“>

<wsdl:port
name=“ServiceSoap“
binding=“tns:ServiceSoap“>

<soap:address
location=“http://intranet/_vti_bin/WebsExtrawsdl.aspx“ />

</wsdl:port>

<wsdl:port
name=“ServiceSoap12“
binding=“tns:ServiceSoap12“>

<soap12:address
location=“http://intranet/_vti_bin/WebsExtrawsdl.aspx“ />

</wsdl:port>

</wsdl:service>

</wsdl:definitions>

And the file WebsExtradisco.aspx:

<%@
Page
Language=”C#”
Inherits=”System.Web.UI.Page”
%>
<%@
Assembly
Name=”Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
%>
<%@
Import
Namespace=”Microsoft.SharePoint.Utilities”
%>
<%@
Import
Namespace=”Microsoft.SharePoint”
%>

<% Response.ContentType = “text/xml”; %>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request) + “?wsdl”),Response.Output); %>
docref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<soap
address=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
xmlns:q1=”http://tempuri.org/”
binding=”q1:ServiceSoap”
xmlns=”http://schemas.xmlsoap.org/disco/soap/”
/>

<soap
address=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %>
xmlns:q2=”http://tempuri.org/”
binding=”q2:ServiceSoap12″
xmlns=”http://schemas.xmlsoap.org/disco/soap/”
/>

</discovery>

And when I browsed the pages http://intranet/_vti_bin/WebsExtradisco.aspx or http://intranet/_vti_bin/WebsExtra.disco was:

</discovery>

Of course, to make the address translation from http://intranet/_vti_bin/WebsExtra.disco actually point to the correct file http://intranet/_vti_bin/WebsExtradisco.aspx and similary http://intranet/_vti_bin/WebsExtra.asmx?wsdl point to http://intranet/_vti_bin/WebsExtrawsdl.aspx the correct setting have to be added to the file spdisco.aspx. This is the version I had (Notice the two last tags before the if-statement):

<%@
Page
Language=”C#”
Inherits=”System.Web.UI.Page”
%>
<%@
Assembly
Name=”Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c”
%>
<%@
Import
Namespace=”Microsoft.SharePoint.Utilities”
%>
<%@
Import
Namespace=”Microsoft.SharePoint”
%>

<%@
Import
Namespace=”Microsoft.SharePoint.WebControls”
%>

<%@
Import
Namespace=”Microsoft.SharePoint.Administration”
%>

<% SPSite spServer = SPControl.GetContextSite(Context); SPWeb spWeb = SPControl.GetContextWeb(Context); %>

<% Response.ContentType = “text/xml”; %>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/alerts.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/alerts.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/alerts.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/Authentication.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/Authentication.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/Authentication.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/copy.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/copy.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/copy.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/dspsts.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/dspsts.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/dspsts.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/dws.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/dws.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/dws.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/forms.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/forms.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/forms.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/imaging.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/imaging.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/imaging.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/lists.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/lists.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/lists.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/meetings.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/meetings.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/meetings.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/People.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/People.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/People.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/permissions.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/permissions.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/permissions.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/SharepointEmailWS.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/SharepointEmailWS.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/SharepointEmailWS.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/SiteData.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/SiteData.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/SiteData.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/sites.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/sites.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/sites.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/spsearch.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/spsearch.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/spsearch.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/UserGroup.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/UserGroup.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/UserGroup.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/versions.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/versions.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/versions.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/views.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/views.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/views.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/WebPartPages.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/WebPartPages.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/WebPartPages.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/webs.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/webs.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_bin/webs.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<contractRef
ref=<% SPEncode.WriteHtmlEncodeWithQuote(Response, spWeb.Url + “/_vti_bin/WebsExtra.asmx?wsdl”, ‘”‘); %>
docRef=<% SPEncode.WriteHtmlEncodeWithQuote(Response, spWeb.Url + “/_vti_bin/WebsExtra.asmx”, ‘”‘);%>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<soap
address=<% SPEncode.WriteHtmlEncodeWithQuote(Response, spWeb.Url + “/_vti_bin/WebsExtra.asmx”, ‘”‘); %>
xmlns:q1=”http://schemas.microsoft.com/sharepoint/soap/directory/”
binding=”q1:ServiceSoap”
xmlns=”http://schemas.xmlsoap.org/disco/soap/”
/>

<%

if (spServer.WebApplication is SPAdministrationWebApplication)

{

%>

<contractRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_adm/Admin.asmx?wsdl”),Response.Output); %>
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_adm/Admin.asmx”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/scl/”
/>

<discoveryRef
ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + “/_vti_adm/Admin.asmx?disco”),Response.Output); %>
xmlns=”http://schemas.xmlsoap.org/disco/”
/>

<% } %>

</discovery>

And when browsing to http://intranet/_vti_bin/spdisco.aspx I got the following result:

</discovery>

</discovery>

So, with these example files, and these tips, I hope I can ease your troubles in making you own custom sharepoint web service.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Problems with read-only fields…

by Gustaf Westerlund | Aug 10, 2007

When creating javascripts in general and when working with AJAX-based javascripts (javascripts that access server based information) specifically, it is not uncommon to update attributes in CRM-forms. If these attributes are “Disabled” using the form-editor or are disabled using javascript in with the following code:

crmForm.all.xxx_myfield.Disabled = true;

Then any updates to the data of this field, will NOT be saved when the form is saved. There is a way to bypass this and this is to set the attribute to “Read only” instead, with the following javascript code:

crmForm.all.xxx_myfield.readOnly = true;

This will disable any editing of the field by the user, but any data that is modified will still be saved.
I have some other stuff I will share with you soon aswell.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Inactivating custom entities in code

by Gustaf Westerlund | Aug 8, 2007

I am currently working with as a sub consultant for what I beleive is Swedens foremost MS CRM supplier, Cybernetics, and ran into some problems when trying to deactivate a custom entity using code. I was unable to find any documentation at all in the latest version of the SDK but after a little searching, I found that Jonas Deibe at Microsoft Sweden, had the solution. Please have a look if you want to know how to do it:
http://blogs.msdn.com/jonasd/archive/2007/04/04/setting-status-with-setstatedynamicentityrequest.aspx

I’ll just give you some code my self:

SetStateDynamicEntityRequest req = new SetStateDynamicEntityRequest();
req.Entity = new Moniker();
req.Entity.Id = yfid;
req.Entity.Name = EntityName.cyb_yearlybusiness.ToString();
req.State = “inactive”; // = Deactivation
req.Status = -1;
service.Execute(req);

I have seen some very interesting “fake lookups” here at Cybernetics aswell, and I will soon be writing about how to create them.

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

No more vacation – but soon Convergence!

by Gustaf Westerlund | Aug 3, 2007

Well, my 7 week vacation/parent leave is coming to an end, as is my low activity on this blog. I’ve been away from a proper internet connection which is why I havn’t been to active. It will be intersting to start working again now, that I have a 7 weeks old daughter at home.

Well, I really like to work with these products and all the interesting customers I have, so it’s not very saddening to go back to work, and I like to be active here as well.

In october I hope to be meeting some of you at Convergence 2007 in Copenhagen. It will be some very interesting days. If you havn’t registered already, please do, it will be very valuable. Have a look at Microsofts webpage: http://www.microsoft.com/dynamics/convergence/copenhagen/default.aspx

I will be staying at Copenhagen Strand, it would be nice to meet some of my blog readers, so if you havn’t already booked an hotel, you could always give it a try. Hope to see you there in person!

Gustaf Westerlund
CRM and SharePoint Consultant

Humandata AB
www.humandata.se

Javascript event handling and dynamic lists in SharePoint

Not so simple SharePoint and CRM integration

Problems with read-only fields…

Inactivating custom entities in code

No more vacation – but soon Convergence!

Recent Posts

Recent Comments

Categories

Meta