 |
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 LAN Client ( RSS)
-
|
The Quick Find functionality in the SalesLogix web client is a fast and easy way to look up information from many different areas in SalesLogix, but did you know you could modify the layout of the various lookups displayed in that interface? The functionality is a little hard to find if you don't know where to look, but this post will explain how you can modify the Quick Find lookups.
|
-
|
In this post I'll outline some of the functionality available to you in the Standard Ticket Activity support script for SalesLogix LAN. As with the other built in SalesLogix scripts, access to this functionality allows you the ability to control the various processes regarding ticket activities.
Most of these functions and methods deal with populating the activity and history tables.
|
-
|
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 a recent project, I used triggers to enforce some data rules in the Ticket area of SalesLogix. We did this because our client was using both the LAN as well as the Web clients. We were having some difficulty seeing changes in the LAN client when values were set in the Web, and vice-versa.
|
-
|
Back in January, I posted about the SalesLogix picklist data structure, and outlined how to use the data found in the picklist table to populate other controls such as comboboxes and listboxes. You can find that article here.) If you are performing customizations to version 7.2 or later of SalesLogx, this processes can be greatly simplified by using Application.Picklist instead of directly querying the database.
|
-
|
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.
|
-
|
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.
|
-
|
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 SplitterPanel control in SalesLogix gives you the ability to partition a view into sections, and gives you the ability to resize the panels at run-time by dragging the splitter line on the control.
|
-
|
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:
|
-
|
For this basics article, I just wanted to outline the differences between the Radio Button and Radio Group controls, and when you would want to use one vs. the other. Both controls provide a similar sort of interface to end users, allowing them to select...
|
-
|
Picklists in SalesLogix are a very useful tool, but did you know you could also you values from an existing picklist to populate other list-based controls such as ComboBoxes, CheckListBoxes, ListViews... even Radio groups? You simply need an understanding of the structure of picklists in SalesLogix:
|
-
|
A combobox control works much like a picklist, in that it presents a number of selectable values to be stored in that control. You can set available values at development time using the items property of the control, but for greater flexablility, you...
|
-
|
It's simple enough in the SalesLogix LAN client to slap a bunch of bound controls on a form, but if you want to perform any sort of action on that data, chances are you are going to be writing code on various events available to you. As a simple example...
|
-
|
I recently had a project where I had to configure an account-level datagrid which displayed a list of related opportunities. Aside from standard opportunity level fields, I also needed to include a simple count of products for each opportunity. In order...
|
-
|
Instead of opening a main view object, you can avoid the delay in opening the form by simply invoking the new form, and then using global variables to pass any necessary information back to the invoked form.
|
-
|
Often times, you need to force a particular type of input to a SalesLogix field. There are a couple ways to do this: If the control is mapped to an numeric database field, an error will be displayed stating that alpha characters are not allowed; otherwise, you can set the format type of the control to ftInteger, but that will not prevent alpha entry. It will only prevent any non-numeric values from being displayed (any non-numeric value would display as '0').
The method I use frequently, is to evaluate the key pressed in the control, and set the control to readonly based on what is being entered...
|
-
|
For my first Blog post (well, I guess technically second), I’m going to keep things pretty simple. If you’re already familiar with implementing customizations in SalesLogix, this will all be old hat. If you’re familiar with common controls in Visual Basic or C#, then this should all seem familiar to you as well. I’ll get more in-depth in the future; but for now, here’s some of the most common controls I use in SalesLogix customizations.
|
|  |
|