 |
Note: this subscription applies to the current blog only.
You will receive each new post via e-mail. Your e-mail
address will not be used for any other purpose.
Browse by Tags
All Tags » SalesLogix ( RSS)
-
|
My colleague Ryan just posted about a simple method to increase the height of picklist dropdowns in the SalesLogix web client.
I have a slightly different way to accomplish the same thing for individual picklists, so while not really more difficult to do, would require you to do it for as many picklists you want to modify. Ryan's solution modifies a stylesheet to affect all picklists in the system at once.
|
-
|
If you work on SalesLogix across a number of remote desktop connections and a number of different workstations as I do, you may occasionally run into an issue where the Properties or Toolbox windows cannot be made visible. This happens when you first start a Remote session from a machine with a greater screen resolution, move one of those windows to the far right of the screen, then start a Remote session on a machine with a smaller resolution. You can then end up in a situation where the propertes and/or toolbars views are technically "visible" but are in a position outside of the current screen resolution.
|
-
|
On a recent project, I worked on emulating functionality similar to what is found in the LAN client where a user is presented a dialog asking them to choose between different activity types then launching into the Schedule Activity functionality. I found this was fairly easy to duplicate in the web client, and in this post, I'll quickly go through the steps for creating that type of functionality.
|
-
|
I've previously posed about a number of useful functions available to you within the SLX_Common script in the LAN version of SalesLogix. I'd like to go a little further in-depth about a couple of functions which are helpful for creating new SQL Query strings.
In a recent project, I needed to build a query interface similar to what you find in standard opportunity products view. The SLX_Common script holds a couple of functions that I used in building this interface. In this posting, I'm going to go through building a simple account lookup view using this functionality.
|
-
|
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.
|
-
|
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.
|
-
|
In this basics article, I wanted to outline the use of include scripts within the SalesLogix LAN client. Specifically, I'm going to look at the standard SLX Database Support script.
|
-
|
If you've ever wanted to modify the email generated from the Opportunity Snapshot in the web client, you'll find that it is incredibly simple to add new fields to the body of the email. To do so, you will need to modify the OpportunitySnapShot.ascx.cs smart part, found under Portal Manager->Sage SalesLogix->SupportFiles->SmartParts->Opportunity.
|
-
|
Ah, the SalesLogix Web Client... Having worked with SalesLogix for over a decade, I feel as though there's not a whole lot I can't do with the LAN client. The Web client however.... Well, it seems like I encounter challenges with it every day.
|
-
|
If you've been following our blogs, such as mine or our others written by Ryan Farley, Kris Halsrud and George Jensen (among others), we now have feeds set up on both Twitter and Facebook! These feeds are a great and easy way to stay on top of new information relevant to SalesLogix, SageCRM and all the great content that comes out of Customer FX.
|
-
|
Did you know that you can include SQL views in SalesLogix? This can be a very handy method to include data that is not normally part of SalesLogix. It is important to note, that these changes are not sync-aware. However if you are running SalesLogix LAN in a network only environment, this can be a helpful way to include data from external sources.
|
-
|
Prior to version 7, there was limited access to those activity and history areas in SalesLogix. In a recent project, I had to perform a series of tasks upon completing an activity with a particular Type/Category/Result combination. This had to be done in an 6.2.1 system. In order to do this, I had to modify the OnCompletedActivity active script. I wanted to briefly wanted to outline the modifications I made to this area, just for anyone who is running an older version of SalesLogix.
|
-
|
From time to time, you may find that you want to reference a control or script on a form other than the one you are currently on. This can be done easily using the Forms collection in SalesLogix.
|
-
|
If you've ever wanted to implement some sort of Spell Check functionality within your SalesLogix database, you're in luck! The Standard Spell Check vbScript makes it simple to add this functionality to your custom forms
|
-
|
In my last blog post, I described how to use the Progress Bar control to provide feedback to a user when running time intensive processes. In addition to the Progress Bar control, the Animate control can also be used. Animate Control The Animate control...
|
-
|
When performing lengthly updates in the SalesLogix client, it's a good idea to provide the user with some degree of feedback so that it doesn't appear as though SalesLogix has locked up. The Progress Bar control, can be used for this purpose:
|
-
|
The opportunity snapshot on the Opportunity Detail view is a handy place to display summary information, but customizing it can be a bit confusing.
|
-
|
In my last Main Views article, I created the detail view as well as the mainview. For this next part, I'll go through creating an insert view, as well as toolbar and menu items for the new SLXProject entity.
|
-
|
While field level security can be used to limit read\write access to fields by using security profiles, another option is to use team membership to determine how to configure controls on the view itself. In this example, I'll outline how to show different configurations of the Account Detail view based on a users team membership.
|
-
|
For my next few blog posts, I'll go through the steps required to create a new main area in SalesLogix.
|
-
|
I wanted to take this blog post to briefly outline the different types of Forms available to you in the SalesLogix LAN client, mostly for anyone who is new to creating views and customizing SalesLogix.
|
-
|
The tab control is very simple to use, yet gives you another way to organize controls on new views you create in SalesLogix.
|
-
|
The Excel application object gives you the ability to programmatically create, modify and manipulate Excel spreadsheets. Use that object with SalesLogix, and you have a powerful tool for exporting SLX data.
|
-
|
By using ADO, you have a powerful resource for reading and storing data in SalesLogix. In this basics article, I'll outline the main components involved in constructing and using an ADO recordset in general, and specifically with SalesLogix . If you've never worked with ADO before, this simple example will give you what you need to incorporate ADO into your own customizations.
|
-
|
Recently, I've been working on a customization which calls for one of a number of Merge Forms to be ran based on certain criteria. This is a pretty simple process, and here's how I did it:
First of all, I need to get the pluginid for the appropriate Merge Form, based on my criteria. This can be found in the "Plugin" table, based on the plugin type of 25, and the name of the Form. In this case, these forms have been created by Admin, so the userid is the standard SYST00000001 value:
|
More Posts Next page »
|  |
|