Sometimes you get really lucky and find someone at your workplace or school or in the community that really knows what they are doing and is willing to show you how to do the same. These are rare gems with any process, platform or situation. With SalesLogix we are lucky to have several of these gems.

Nicolas Galler is certainly one of them. Not only has nick maintained his own blog for a while now, but he has also recently contributed to the community.

Great job Nick!

So if you are looking for a step by step definitive guide to Custom From Development – check out the community posting by Nick. No need to repeat the information here :)

No. It isn’t.

By default SData will use Digest Authentication. We talked about this a bit already here.

Enable it

In the web.config you can change the following section:

		<httpModules>
			<clear/>
			<add name="Session" type="System.Web.SessionState.SessionStateModule"/>
			<add name="AppManager" type="Sage.Platform.Application.UI.Web.AppManagerModule, Sage.Platform.Application.UI.Web"/>
			<add name="BasicAuthenticationModule" type="Sage.SalesLogix.Web.SLXWebBasicAuthenticationModule, Sage.SalesLogix.Web"/>

This allows the BasicAuthenticationModule to do it’s thing.

I am working on a Process Orchestration webinar for tomorrow and I figured I would test out some of my existing customizations on my new image. I opened up the solutions, changed all the references to the new versions, compiled and was happy to see the workflow compiled just fine! I went ahead and updated the processstart.xml and processlib.xml and restarted all of my services and loaded up the website to test. My process was registered and I made a change to division and expected a new to-do to appear. It did not. So I changed AccountName and expected the same. Nothing.

What to check?

First check to make sure you restarted at least the DBEventing Service. I restarted the SalesLogix System service just to be safe. I also restarted the web publishing service, but I used IISRESET for this. I knew my assemblies were loaded by looking here: http://localhost/ProcessHost/processmanager/registeredprocesses .

I could see the changes being captured by looking for .task files here:
C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync\QUEUEFiles

I had several.

console mode for dbeventing

I found out from QA and they from Dev that you can run C:\program files\saleslogix\dbeventingservice.exe as console by adding /console to the end. Make sure that the dbeventingservice is shut down prior to doing this and then just enter the above in a run window or make a shortcut.

This will open dbeventingservice in console mode and let you see what it s doing:

You should see your files being picked up and run. I am told that this service is really just a file watcher. It looks for the files to be dropped by process host and then run – little more than that.

In my case it was simply a configuration problem. I was running dbeventing with too low permissions. I updated it to run as webdll (or service) and all was well.

So we have completed our first set of SData Master’s Series classes and they have been a great success.

One of the points of this blog is to answer questions that do not fit into the various videos we have on SalesLogix in the Developer’s Subscription or in the various classes we offer for SalesLogix Web, Lan, Mobile, VA or even .NET Fundamentals.

Where do we put the client libraries?

The question was as simple as that. You get a DLL with the SalesLogix SData Client Libraries — where does it go?

The answer is easier than you might think: It goes somewhere that the application that references it can use it. Just like any other .NET assembly you would probably place it in the bin of the application using the client libraries or in the GAC if you have multiple applications on the same machine using it.

Why the confusion?

I think the confusion is due to the fact that people think the SData Client Libraries modify SData in some way. They certainly do not. They make consuming an SData feed or portal easier for the developer, so they go with the consuming application.

What are the considerations?

The considerations are that you must be using the correct version of the client libraries for the version of the SData portal for the version of SalesLogix you are using. This will be handled by the official delivery of the SData Client Libraries – which is coming soon through the partner community.

Right now we are talking about SData version 1.0 and SalesLogix web version 7.5.2.

In the meantime you can get them as part of the classfiles for our SData Master’s Series on SData here: Classfiles