The SLXGridView control (the older of the 2 controls available in the Infor CRM web client) inherits from the standard ASP.Net GridView as Ryan detailed. Knowing what this control is we can then identify how to change the column header dynamically. This is normally set during the RowDataBound event, however we can also access this […]
In my previous post, I mentioned how to get the selected ID of a gridview’s row when you click the row. Since then I have found that sometimes SalesLogix will implement an extra DataKey in the grid when it is deployed as a quick form. (For instance, if you specify the grid’s DataKeyNames = “Id”, […]
SalesLogix has a couple of numeric based custom text controls including currency, and numeric. One of the things you will find is that using these controls gives the user a slightly different experience based on the custom control chosen. One of the big differences is that the currency control enforces numeric input once the user […]
If you have ever added code similar to: mygrid.Sort("CreateDate", SortDirection.Descending); You may have seen an error similar to this: System.Web.HttpException: The GridView 'mygrid' fired event Sorting which wasn't handled.
I recently ran into a situation where I had built several quick forms on the SalesLogix web that contained lookups. Once the quick forms were deployed to a web site, when attempting to use the lookup the lookup would open with the defined lookup columns, however, regardless of search criteria entered no results would show. […]
In the SalesLogix web client it is often the case where you want to dynamically restrict a control based upon some property of the current entity. For instance, lets say I have a Widget screen and on that screen I want to identify the Account that owns the widget and the Contact at the Account […]
The SalesLogix grid control exposes an OnRowSelected event during design time to allow adding code when a row is selected. This functionality allows you to build out additional functionality around selecting a row, other than just bringing up an edit dialog. In doing this you could for instance have a memo next to a grid […]
These hotfixes are now available for download on the SalesLogix support web site…SalesLogix v7.5.1 Hot Fix 22 corrects a SpeedSearch error that occurs on lead conversion where insufficient resources exist. SalesLogix v7.5.1 Hot Fix 31 includes several fixes for the SalesLogix Provider. Refer to the Applying Guide for more details. SalesLogix v7.5.1 Hot Fix 32 […]
The SalesLogix GridView control does not offer settings fro controlling the width of columns placed within it during design time. Apparently, the though was the control does such a fine job of auto-sizing the grid that exposing those kind of properties was not needed (It is). There is a way of doing this, though it […]
In a recent post I wrote about being careful about what names you give your Entities to prevent them from conflicting with other assemblies or classes that are used by the SalesLogix Web application. On a similar note, I thought I should share another potential conflict that occurred recently. We had a client you had […]
I recently ran into a problem where after adding a new custom entity to a system I was unable to do a build in the application architect. I was suddenly getting errors like: C:Documents and SettingsuserApplication DataSagePlatformOutputimplementationAccount.cs(159,23):The type name 'Int32' does not exist in the type 'Sage.SalesLogix.Entities.System'
In the SalesLogix web grid control there is a TextFormatString property to grid columns. Unfortunately there is no documentation currently on how to use this property. Hopefully this article will help with that. In the SalesLogix Application Architect, if you open a QuickForm that has a grid, you can click on the Grid to […]
OK so you are using the SalesLogix web client and you are searching for records using the standard group/list functionality available on the main pages like Accounts, Contacts, Opportunities. You might say to yourself "Self, great I can find records, and look I can see some columns. You know what would be helpful? If my […]
Ever seen this error message? You will get this in SalesLogix 7.5.1 when using Code Snippet Action Items (Not C# Snippet Action Item which are now tagged as obsolete even though they are nothing of the sort). The problem comes in if you add a new Code Snippet item and then later remove it. You […]
I recently was asked to add a permanent filter on the add opportunity product screen to control what products were available to a user. The requirements called for only certain products to be visible to some users while other products were available to other users, and still other products were available to all users. This may sound complex but it is actually pretty easy, provided you know where to start.
SalesLogix offers the ability to open a "popup" dialog window in the SalesLogix web client. There is a limit currently, only allowing one open dialog window at a time. If you want a popup from a popup it can not be done right now. To launch a popup dialog you can use the the DialogService.
The Page.Session object in ASP.NET allows you to save data per user that requests a page from the SalesLogix web client application. Variables stored in the session object are not discarded when users move between pages. The variables will persist for the length of time the user is in the SalesLogix web client, or until […]
In the SalesLogix web client (7.5 and 7.5.1) if you have a picklist control that uses a picklist with entries containing commas, the picklist value before the comma is shown, the rest is not visible. Sage has just released a hot fix for this issue along with several other items. This is hot fix 24 […]
In my last post I talked about how the lookup control can have multiple conditions added to filter the lookup results. This is done using Prefilters. However, these conditions are appended together with AND logic. Today I want to talk about a method for building OR logic so that a lookup can, for instance, only show those accounts where the type = customer OR the type = prospect.