Login /
Register
 search
 syndication
 about
|
|
 |
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# » SalesLogix Web ( RSS)
-
|
Recently, I had a request to create export functionality for a datagrid in the SalesLogix web client. I had a little difficulty exporting data from the actual grid, but as an alternative, we put together functionality to export data based on a provided SQL query. (Thanks to Ryan for working out the SmartPart code)
By creating a new custom smartpart, we can simply export the results of a SQL query to a CSV file, save it on the webserver and download it to an individual client.
First, you'll want to create a folder on the web server to hold the exported file. In this case, I'm exporting contact data based on the current account, so I created an export folder under the SupportFiles/SmartParts/Account folder in the portal manager.
|
-
|
On a recent project, I worked on emulating functionality similar to what is found in the LAN client where a user is presented a dialog asking them to choose between different activity types then launching into the Schedule Activity functionality. I found this was fairly easy to duplicate in the web client, and in this post, I'll quickly go through the steps for creating that type of functionality.
|
-
|
It's easy to access the UserService interface from a Code Snippet Action item in the SalesLogix web client. For this example, I'm just going to add a button on account detail which will launch a DialogService message with the current user.
|
-
|
Before I get back to Sage CRM topics, I wanted to mention an issue I bumped into an issue in a couple of SLX 7.5.1 databases. Account Type/Subtype combination are generally pretty easy to set up. You just need to create a picklist and name it using the "Code" value for an item in the Account Type Picklist. (For "Lead" for example, create a picklist named "Account Lead" for example). This works fine in most cases, however I discovered that on the insert contact/account screen, it doesn't quite work correctly.
|
-
|
For this post, I'll outline how to use a business rule to enforce field requirements on a Insert view in SalesLogix web
|
|  |
|