Login /
Register
search
syndication
about
|
|
 |
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 » Customizations » Basics ( RSS)
-
|
I wanted to run through quickly how to set filters when using the OpenDialog in the SalesLogix LAN client. When using OpenDialog, it's nice to be able to define filters so that your users only see the type of file that you want them to open. This is really easy to set up.
|
-
|
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.
|
-
|
Over the next few weeks, I'll be posting a walk-through which will outline building a Workslips module for Sage CRM. In this part, I'll cover creating a new table, and defining fields in that table. We're going to start with creating new table structure to hold basic Workslip information. First we have to define the Workslip table. In Sage CRM, got to Administration->Advanced Customization->Tables and Databases and then click the "Create Table" button
|
-
|
I wanted to take this post to outline some of the common field types that are available within Sage CRM, for anyone new to development within Sage CRM. These are definedunder the Fields tab under Administration/Customization/{EntityName}.
|
-
|
On the last Sage CRM project I worked on, I ran across a little issue with the CRM interface which was causing me a bit of a headache. I was working with a couple of screens I had defined for a custom entity. These screens were similar, so I was doing a lot of comparing one screen to another. Every once and a while, I would notice that the screen contents would disappear from the screen I was reviewing, and I would end up having to rebuild the screen.
|
-
|
In my last blog post, I outlined how to display data from external database in Sage CRM 200. This week, I'm going to do the same thing, but instead of connecting to an external datasource through SageCRM, I'm going to display the data using a custom ASP page.
|
-
|
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.
|
-
|
I recently had a project which required me to populate the strings collection in an AutoComplete control from data contained in the database. I wanted to take a second to outline how I populate the control's strings, as well as create a reusable script to simplify the process in the future
|
-
|
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
|
-
|
I wanted to quickly outline a process for passing a condition to a Crystal report in two simple steps. Say you've created an account report that you want to launch via a button on the account detail, limited to the current account record.
|
-
|
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.
|
-
|
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 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.
|
-
|
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...
|
-
|
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...
|
|  |
|