-
In the SalesLogix web client in 7.5.3, the Common tasks that appear in in the list and detail view for an entity are defined in the Common Tasks Tasklet. Today I will show you how to add the standard group tasks of “Save Records as Group”, “Promote to...
-
Sorry for the long absence, I went away on some training with the Minnesota National Guard. This is the fifth post in series that is covering the use of a reporting tool called Stonefield Query for Sage SalesLogix. If you would like to take a look at...
-
A quick overview of the new Promote to Dashboard feature in the 7.5.2.3 SalesLogix web client.
-
In my last post , I briefly went over the new security roles available in the 7.5.3 SalesLogix web client. In this article I want to discuss how to secure a page and utilize this feature to control what screens a user has access to. In the Application...
-
I recently had to build a datagrid displaying ticket information, including the current Status value. Under tickets, the Statuscode field contains the itemid from the picklist table rather than the actual text value as is stored for the Account, Contact or Opportunity areas. If you've only dealt with picklists in those other areas, it could cause some confusion when trying to determine just how to display the Ticket status text value in a datagird, however using the picklist column type makes this very easy.
-
An overview of the new feature security implementation in the SalesLogix 7.5.2.3 web client.
-
One of the really, really, really, really cool new things (did I mention it is cool) that the forthcoming 7.5 SP3 web update provides is a user configurable dashboard interface. Those of you that have used the SalesLogix LAN client have surely seen the...
-
At times I have been asked how can I increase the performance of SalesLogix. For systems using SQL2005 or SQL2008 the slowdown may be corrected by adding an index to the table that the SalesLogix script queries. The trick is finding where the bottleneck resides.
-
The last couple of weeks I have been working on a series of posts introducing Stonefield Query for Sage SalesLogix. The first two posts have been focused on set up and interface layout. Last week we created our first report . This week we are going to...
-
In the last post in the Git for the SalesLogix Developer series, I outlined how to set up a repository. Once that is complete, other developers can use that repository to collaborate on the project. This post outlines how to use a repository and bring it locally so you can use it for development.
-
I have been using the SalesLogix SP3 RC Application Architect for a while, and in general it seems to be pretty stable but today I ran into an issue that prevents you from wiring up external assemblies against Business Rules and Events. The issue seems...
-
Last week I blogged on the deployment of the Disconnected Web Client. Today's post discusses the issues that could arise on the Installation of the Disconnected Web Client. If you have deployed in Application Architect and ran the sync server then the remote users should be able to run sync, apply the changes, and open the personal web server and then the SLXClient.
-
If you've been following along in the Git for the SalesLogix Developer series, you should now have Git installed and configured. Now it's time to start putting it to use. In this post (and included video), I will outline the steps to take an existing SalesLogix project and put it under Git source control. Setting up the initial repository is not a hard task, but knowing all the steps is the only way to get it done.
-
The last couple of weeks I have been working on a series of posts introducing Stonefield Query for Sage SalesLogix. The first two posts have been focused on set up and interface layout. This week we are going to actually dig in and create our first report...
-
In this second post in the "Git for the SalesLogix Developer" series, we will be taking a look at how to install and configure Git. This tutorial will give you everything you need to know if you are new to Git so you can get it all set up and ready to use. In a later post we'll look at how to use Git, but it all starts with knowing how to get started.
-
What we are looking at today is one aspect of the entire Disconnected Web Client piece. We will assume that the remote users have already been created
-
How SalesLogix web view users have access to areas controlled in the SalesLogix 7.5.2 web client.
-
An exception occurred executing the dynamic method Lead.SaveLeadHistory.: Transaction not successfully started. Error occurring in the SalesLogix web client and the reason for it.
-
Last week I wrote about my experience downloading and setting up Stonefield Query. This SalesLogix reporting tool has been around for years and I thought it was time to take a close look at the tool and its capabilities. I am still in the introductory...
-
If someone has deleted an existing SalesProcess and you need to restore it you can follow this guide.
-
Just a quick post about how you can control visibility of a server control on a SalesLogix web page using the Style attribute.
-
Since reporting is one of my interests I always tend to take notice when I hear of a reporting tool. A few weeks ago Scott Weber , Customer FX's own CRM Practice Manager and Senior Consultant, introduced a product to me called Stonefield Query. It...
-
The SLX_Common script included in SalesLogix contains a number of simple, yet useful, functions that you can use within your own functionality to save yourself some time by not having to reinvent the wheel each time you need some simple functionality.
-
The SalesLogix SLXUserService class in the Sage.SalesLogix.Security assembly allows you to get a reference to the current user’s IUser interface. With a reference to the current IUser interface you can then check the user’s Type property to see what type of User license the user has.
-
If you have ever tried adding a reference to an external assembly in the SalesLogix entity model through the Application Architect and have received the error: Could not load file or assembly 'file:///Somepath\SomeAssembly.dll' or one of its dependencies...