 |
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)
-
|
For some who have been working in the SalesLogix LAN client for years, the transition from using SQL queries to retrieving data using a repository with the entity model can be a difficult change. This post will look at some common data retrieval methods and the SQL equivalents to help you get your head around how to get work done using the entity model.
|
-
|
Creating modules for SalesLogix Web is something that is likely something that is often overlooked or not used because they are assumed to be too complex or are just not understood. A module is an assembly that you've added to a page or the portal that adds functionality to the page. The great thing about a module is that you can change things about the page without needing to resort to doing something like modifying the deployed pages or SmartParts. This article will look at how to create a module to conditionally hide a menu item at runtime.
|
-
|
There are many reasons why extracting a SalesLogix Report from the SalesLogix database might be useful. There are possibilities of integration, automated running of reports, as well as the need to generate a PDF from some code on a server using a SalesLogix Crystal report. This post will show you how and show you the code to do it.
|
-
|
Five years ago I wrote a post about how to determine if a user is a member of a team in SalesLogix LAN scripts that is still referred to today. I've been asked on occasion how one would go about doing the same in the SalesLogix Web platform, so I thought it was time for a follow up post. In this post I will demonstrate how to use a HQL query to create a reusable function in the SalesLogix Web platform to determine whether a user is a member of a specified team.
|
-
|
There are likely many cases in SalesLogix Web where you need to access properties on the User and Security related entities that are not included in the entity by default, meaning that there is no public property exposing the value. For example, the IsManager property on the User entity. Modifying these entities won't work, so how do you get to these properties? This post provides an explanation of why you can't modify these entities and how to get to these property values.
|
-
|
I announced a while ago that we will be offering some public developer training classes for SalesLogix Web. We will be making some changes to the class outline I posted earlier.
|
-
|
Ever since the new SalesLogix 7.2 Web client and platform was released, I've had numerous requests for development training. Until now, I've done that on a very individualized basis, providing web training to single companies at a time. I've decided that it is time to make my web development training classes public, and I'd like your feedback.
|
-
|
There are many ways to get the "current" account in SalesLogix Web. For those coming from developing for the SalesLogix Windows client, you'll likely want the same capabilities that the BasicFunctions CurrentAccountID provides. In the web platform, however, there is all of that, plus more.
|
-
|
One of the best things about working with the SalesLogix 7.2 Web application is how great the entity model is. You have this single place to put all your rules and logic, the UI is really just an afterthought. Something that I do quite often is create business rules to return data specific to an entity instance. For example, a rule to return the primary contact for an account. Let's take that a step further and return a list of objects from an business rule. For this scenario, we'll create a business rule that will return a list of child accounts for the current account instance.
|
-
|
In my last post, I shared some code in VBScript to PING a remote server to check for availability before attempting to use a resource on that remote server. This wouldn't be my blog if I didn't also share this code in C# as well. IMO, this sort of thing is a far better suited for a .NET Extension if for the SalesLogix Windows client.
|
-
|
I've released a free addon for SalesLogix 7.2 Web for account relationships. The account hierarchy screens that exist in the SalesLogix Windows client is missing for the SalesLogix 7.2 Web Client. This bundle will bring this functionality into the web client. The addon works exactly the same as this functionality in the windows client. Full source included.
|
-
|
I've been using the following C# class for creating SalesLogix table ID values lately and I just love the elegant syntax it provides. It's really been growing on me. Here is the class: using System; using System.Data.OleDb; namespace SalesLogix...
|
-
|
Over the past several years I've maintained a SalesLogix related weblog at SalesLogixBlog.com. This blog has now moved to a new URL and a new perspective. SalesLogixBlog.com can now be located on the new Customer FX 3.0 website at http://customerfx.com/crmdeveloper.
|
-
|
I posted before about getting previous values for entity properties in SalesLogix Web. The method I used in that post made use of IEntityState to get the changes for an entity. In SP2 (version 7.2.2 - currently in release candidate as of the time of this post) IEntityState is now obsolete. It has been replaced by Sage.Platform.ChangeManagement.IChangedState. All SalesLogix entities now implement this interface.
|
-
|
If you have been working with SalesLogix 7.2 Web, you've probably discovered the lack of documentation and ran into several frustrating and painful moments where you were not quite sure how to accomplish what you needed. I'll let you in on a secret. You have all the documentation you need - well, maybe not all you need, but you do have a lot.
|
-
|
A question was asked in the SalesLogix Business Partner newsgroups about how you would go about adding the Primary Contact for an account to the AccountDetails form. I thought this was a great idea for a post since there are many ways to go about doing this, some of them better than others. Your first reaction might be to write some code on the form, in a LoadAction, to set a control with the value of the account's primary contact. However, you'll find that you have the easiest time, now - and w
|
-
|
Field change tracking is implemented in a great way in SalesLogix 7.2 Web. You select the entity you want to track field change history to and then select the fields to audit. It's that simple. You can also easily create your own custom tracking tables to record field changes to so you don't have to overload the history table with all the tracked field changes.
|
-
|
It seems that many of the customizations I've done for customers to date include building functionality that exists in the SalesLogix Windows client, but does not yet exist in the Web client. Things such as account products, parent account hierarchy, etc.
|
-
|
Nicolas Galler posted some invaluable info on the lifecycle of SmartParts that inherit from EntityBoundSmartPart. This info just saved me some headaches today even.
|
-
|
If you've implemented the new SalesLogix 7.2 Web Client, chances are that you've heard complaints from your end-users about the way that required field validation appears when attempting to save a record. You've probably heard, I click Save and nothing happens - they don't notice the little red asterisks next to the required fields that did not validate.
|
-
|
I would imagine that it is a common request for many companies that use the SalesLogix customer portal to allow their customers to create tickets to want to bypass the login screen since they might be launching the customer portal from some other customer site where the customer has already logged in. This is a reasonable request. If you've already validated the customer when they logged into some other customer portal or site, you don't want to have them log in again when you launch the custome
|
-
|
When a field is changed in the 7.2 web client, you often will find scenarios where you will have business rules that need to validate the change and possibly change it back to whatever it was before. Checking the property on the entity, you'll find it is too late. The property will already show the new value it was changed to. Fortunately, the 7.2 platform maintains state for all entities, so it is possible to easily retrieve the previous value for a property.
|
-
|
In the SalesLogix 7.2 Customer Portal, you might have the need to get or set values from the user's contact record. While the user is actually a contact, in the portal, the SLXUserService is still used to get the logged in user, however, you'll need to translate to an IContact to work with the underlying contact record.
|
-
|
Adding custom SmartParts in SalesLogix 7.2 Web is an easy task. However, a little extra effort can make it look polished and complete. Adding an icon to your custom SmartPart can add an additional professional look, with little effort.
|
-
|
Using 7.2.1, if you change the portal title this change does not reflect as the title of the deployed site. For example, if you change it from "Sage SalesLogix" to "SalesLogix Development System", then deploy the site, it will still show "Sage SalesLogix" as the site's title. I should mention, this was not a problem in pre-SP1 (7.2.0) systems it worked fine there.
|
More Posts Next page »
|  |
|