Tag: slxdeveloper.com

Customer FX Corporation announces slxdeveloper.com reached 3,000 members earlier this month, making it the largest community on the web dedicated to developers who work with Sage SalesLogix.

If you're working with the new SalesLogix 7.2 Web Client & the Application Architect then the place to be is the slxdeveloper.com forum for the SalesLogix 7.2 Web. It has some really great discussions going on. One of these great discussions is where an slxdeveloper.com member needs to make the phone numbers hyperlinks. A user can click the phone number to launch a browser window, passing the phone number, to initiate a phone call. Let's take a look.

The wait is finally over. SalesLogix version 7.2 is finally released. This new version brings an exciting new ASP.NET based webclient and a ground-breaking, and completely incredible new development .NET environment - the Application Architect. I'll have plenty to say in the months ahead about this incredible new version of SalesLogix, for now, here's some of the important dates

I came accross a tip today that I didn't know about the SalesLogix web client in the slxdeveloper.com forums. I had no idea you could do this, but appearently this has been around since version 6.2.3.

A really great thread has been evolving in the slxdeveloper.com forums about consuming web services from SalesLogix VBScript plugins.

I put together a new utility I'll be releasing in the near future on slxdeveloper.com called SalesLogix FormSpy. Have you ever needed to customize a form but you didn't know what the form's name was? That is what this utility will solve. FormSpy is a .NET app that runs in the background. While SalesLogix is open it draws an overlay on the top-right corner of all customizable forms. The overlay will show you that the form is customizable (it doesn't put the overlay on non-customizable forms) and

I just thought I would post an announcement here that I've launched forums on slxdeveloper.com! They are a long time coming but I finally managed to squeak in enough time to finish them up.

Not too long ago I wrote an article on generically setting a Form as read-only on slxdeveloper.com. Mike Spragg from E1 Business shared a great approach with me to accomplish the same with legacy views.

I recently posted an article on slxdeveloper.com where I outlined the code for a class for SalesLogix to set an entire form as ReadOnly at runtime (See Generically Setting a Form as Read-Only). I put that code to some cool use this week when I needed to set an entire MainView as ReadOnly based on certain conditions.

If you have not yet read Stuart Carnie's article on slxdeveloper.com on using prepared queries with the SalesLogix provider than I highly recommend you check it out (See: The Myths and Legends of Prepared Queries). Stuart recently offered some comments to the article which provided some background on the provider in regards to trips to the server as well as other significant changes which result in big performance gains.