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 » Application Architect ( RSS)
-
|
Often when adding custom code to SalesLogix you need to reference Assemblies that are not included by default in Code Snippets or action items. This problem will often manifest itself with an error when building like “The type or namespace name 'Data'...
|
-
|
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...
|
-
|
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...
|
-
|
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.
|
-
|
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.
|
-
|
How to fix the error logging into SalesLogix Application Architect- 'evt://Projects/ActiveProjectChanged'
|
-
|
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...
|
-
|
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.
|
-
|
In Brianna's post she mentioned how there is new functionality in SalesLogix 7.5.1 called filters. I wanted to explain what exactly this change is and how it impacts the use of SalesLogix.
|
-
|
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...
|
-
|
So you have just finished developing a web solution, have created a web manifest with your myriad of changes and you go to save the manifest. Then you see...
|
-
|
The SalesLogix 7.5 web entity model, unfortunately, does not have access to a user's manager by default. Trying to expand the SalesLogix entity model is often problematic as the changes to the entity layer do not correctly compile into the security...
|
-
|
In the SalesLogix 7.5 web, you can add a radio group control to allow for selection of options on screen. This control can be bound to either write to a field in the database upon the selection being made or it can be unbound to prompt the user to make a choice that can then drive other on screen actions.
|
|  |
|