 |
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 » Development ( 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.
|
-
|
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.
|
-
|
Using pivot queries in SQL is a great tool for rotating data, but what if you need to do something more complicated with multiple data sources and multiple columns? Recently, I had a request to pivot some data from multiple similar tables and to rotate that data into a columnar format.
|
-
|
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 just finished work on an import project into SageCRM, using SQL Server Integration services to move data from a couple of Excel Spreadsheets into the database. One of the items I had to figure out was how to populate tableIDs for the imported records.
|
-
|
Recently, I worked on an import where I spent a considerable amount of time working out how to effectively parse data from a SQL table, for insertion into another table.
|
-
|
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.
|
-
|
In this post, I will outline a relatively simply process for displaying data in Sage CRM from an external data source.
|
-
|
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.
|
-
|
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.
|
-
|
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.
|
-
|
For this post, I'll outline how to use a business rule to enforce field requirements on a Insert view in SalesLogix web
|
-
|
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.
|
More Posts Next page »
|  |
|