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 » C# ( RSS)
-
|
Showing a message to a user in SalesLogix Web is an easy task. It should be, right? Of course - and it is, however, you might need to know where to look to do it. This post will take a look at how to do this from both a Code Snippet Action and a C# Snippet Action.
|
-
|
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.
|
-
|
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.
|
-
|
Something that is a common task in development, yet one that I get a lot of questions about, is how to programatically add a new record in SalesLogix Web using the entity model. This is an easy task, but unless you have some examples to learn from you...
|
-
|
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.
|
-
|
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 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...
|
-
|
Many people who customize SalesLogix have become accustomed to using the built in "SLX Database Support" script to provide things like the quick and easy GetField function to return a single database value. If you've ventured into the .NET Extensions realm, you might want an easy equivalent. The following is a repost of something I posted around a year ago in the Sage Business Partner newsgroups
|
-
|
A change was introduced in 7.2.2 regarding custom properties. This post looks at this change and revisits the earlier topic of placing a link to an account's primary contact on the account details form.
|
-
|
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.
|
-
|
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
|
-
|
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.
|
-
|
When a SalesLogix user logs into the SalesLogix 7.2 Web Client for the first time, they will, by default, end up at a blank area since they have not yet selected a default in their user options (Such as the account or contact area). Chnaging this behavior is a simple thing as long as you know where to do it.
|
|  |
|