The SalesLogix entity model allows you to add an event/business rule action to a public method in an external assembly. This post talks about how to do this
Programatically Creating a Temporary Lookup Group for a specific entity in the SalesLogix web client
In SalesLogix you will often see behavior where after saving a record your are taken to the detail view of the new record and the current group has been set to just the new record. In the LAN client there was a Application.BasicFunction method exposed to do this. In the web client there is not […]
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’ does not exist in the namespace ‘System’ (are you missing an assembly reference)” […]
For anyone who uses Git Extensions for SalesLogix, I've released a small update that adds some core functionality and makes it possible to complete the entire scenario of setting up and using Git with a SalesLogix project - all from within the SalesLogix Application Architect!
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 […]
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.
Yesterday I announced my new project Git Extensions for SalesLogix. I received a lot of e-mails from people who read that post, so I thought it would be a good idea to record a quick video so you can see it in action and get a better idea how it works. This quick 4-5 minute video will show you how to commit changes in Application Architect to a Git repository and push the changes to an online repository as well, all from inside Application Archit...
This blog post is the first of many that will cover the topics of using source control with SalesLogix development, Customer FX's open source initiative, and the new Git Extensions for SalesLogix module for Application Architect. These are three things I am completely excited about. Using source control with SalesLogix development in Application Architect is a necessity if you want to do it right. Git Extensions for SalesLogix is the first of...
I just came across some new info that has been added to SalesLogix 7.5.2 (currently in beta). The ability to add custom controls to Application Architect for use on QuickForms. This is a completely welcome and awesome addition to the SalesLogix Application Architect. The following is taken from the 7.5.2 AA help files...
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. To add an custom entity property, expand out the VFS…Entity Model…Packages…SalesLogix Application Entities. Right click on properties […]
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 to bind the lookup to a SalesLogix entity to look up records within […]
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 web client is setting the close probability. Since we […]
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 ke...