Login /
Register
 search
 syndication
|
|
 |
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 7.5 ( RSS)
-
|
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...
|
-
|
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...
|
-
|
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 Settings\user\Application Data\Sage\Platform\Output\implementation\Account.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...
|
-
|
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.
|
-
|
The SalesLogix entity model offers the ability to create a custom property underneath an entity. This can be useful for automatically rolling up things like the Opportunity Sales Potential or calculating fields such as the Opportunity Weighted Average...
|
-
|
The following is a brief overview of the SalesLogix Lookup control and how to use it in the SalesLogix web client. Determining the Lookup type The SalesLogix SLXLookup web control is built upon the standard ASP.Net Lookup control. It offers the ability...
|
-
|
An overview of how definitions set for a Page in the Portal Manager in the SalesLogix Application Architect actually get rendered out to the web site during deployment.
|
-
|
I recently encountered an issue where a user (in this case Admin) logging into the SalesLogix 7.5 LAN client would have the application crash once the user attempted to navigate to the Accounts area in SalesLogix. I discovered the reason for this was multiple entries for the user in the USEROPTIONS table.
|
-
|
How to fix the error logging into SalesLogix Application Architect- 'evt://Projects/ActiveProjectChanged'
|
-
|
We recently had a client who had requested the add product dialog in the SalesLogix web client have specific values defaulted when the screen first opened. The add product screen is not a Quick From but is a custom smart part with a separate code file...
|
-
|
How ERP Link determines warehouse values when posting a Sales Order to MAS 500 from SalesLogix
|
-
|
ERP Link will not work with SmallInt data types, even though they are a valid SalesLogix data type and can be selected when adding a field to the database in the SalesLogix Workgroup Administrator.
|
-
|
In an earlier post , I reviewed the ERP Sync component of the Sage ERP Link product. We had a client who was unable to get ERP Sync to run. They had everything set up correctly but when the job was executed using the command line switches...
|
-
|
As you probably know, SalesLogix displays most date times in the database in UTC format. Normally the SalesLogix provider handles converting the UTC formatted dates to the local client date times. There are exceptions to this automatic adjustment. One such case is the Journal tab within the Ticket area of the SalesLogix web client.
|
-
|
How to set the current group in the SalesLogix 7.5 web client
|
-
|
While there are many ways of querying data in the SalesLogix entity model, including using the DataServices, or IQuery to run a direct query to the database, SalesLogix also has provided a Picklist assembly for working specifically with picklists.
|
-
|
As Ryan briefly mentioned in this post , the EntityFactory allows you to retrieve entity objects from within the SalesLogix entity model. The EntityFactory allows you to retrieve an existing entity collection or to create a new record...
|
-
|
I was recently helping a client setting up picklist attributes in the SalesLogix 7.5 web client using techniques I described in this post. After we were done making the necessary modifications she went on to test out her changes in the web client. She reported back an issue that I have since replicated and verified still exists in the SalesLogix 7.5.1 web client.
|
-
|
Anyone who has worked with SalesLogix knows about managing picklists in the LAN client and how you can manage what items are available in a list and what attributes the list has. The SalesLogix 7.5 web introduces a new paradigm for managing picklists - kind of.
|
-
|
In this post I discussed how the SalesLogix 7.5 web client modifies close probability different than the LAN client. I now want to talk about how you can change this behavior to match the LAN client. The first thing we need to understand is how the SalesLogix...
|
-
|
In the SalesLogix 7.5 web client, when a user sets the status of an opportunity to "Closed - Lost", the system will automatically change the close probability to 100%. This is different than the behavior in the SalesLogix 7.5 LAN client. In the LAN client when the status is set to "Closed - Lost" the probability is set to 0%.
|
-
|
After developing in SalesLogix 7.5 web long enough you will come across one of the OOTB screens that are not editable Quick Forms or will need to build your own custom SmartParts. These custom SmartParts are useful in they allow much more flexibility then is available in a Quick Form, however you must modify the code directly without a graphical interface. When it comes time to bundling these custom SmartParts there are a couple of things to keep in mind.
|
-
|
When adding or removing items from a SalesLogix 7.5 web manifest, it is important to note that the Application Architect is not very good at properly cleaning up after you, nor is it good at adding to items to a "dirty" manifest. To try to make...
|
-
|
One of the nice things about the bundle model concept in the SalesLogix Application Architect, version 7.2 and up, is the ability to drag items that have been modified into a bundle. For instance, if you have added custom entity properties to the...
|
More Posts Next page »
|  |
|