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 » Sage CRM ( RSS)
-
|
I was recently doing some work on merge forms in SageCRM and discovered that for Cases, SageCRM didn't take into account different address types in the OOTB Case merge fields. Normally, Address information is derived by joining the case_PrimaryCompanyID to the Company table, and then joining from Comp_PrimaryAddressID to the address tables. With these joins, you could only include the primary address for the Case's account, however I wanted to display both Shipping and Billing addresses as well.
In this post, I'll go through the view changes I made to include Billing and Shipping Addresses on this merge form.
|
-
|
I just finished work on an import project into SageCRM, using SQL Server Integration services to move data from a couple of Excel Spreadsheets into the database. One of the items I had to figure out was how to populate tableIDs for the imported records.
|
-
|
If you've been following our blogs, such as mine or our others written by Ryan Farley, Kris Halsrud and George Jensen (among others), we now have feeds set up on both Twitter and Facebook! These feeds are a great and easy way to stay on top of new information relevant to SalesLogix, SageCRM and all the great content that comes out of Customer FX.
|
-
|
Over the next few weeks, I'll be posting a walk-through which will outline building a Workslips module for Sage CRM. In this part, I'll cover creating a new table, and defining fields in that table. We're going to start with creating new table structure to hold basic Workslip information. First we have to define the Workslip table. In Sage CRM, got to Administration->Advanced Customization->Tables and Databases and then click the "Create Table" button
|
-
|
I wanted to take this post to outline some of the common field types that are available within Sage CRM, for anyone new to development within Sage CRM. These are definedunder the Fields tab under Administration/Customization/{EntityName}.
|
-
|
By using the Systems Menu functionality, you have the ability to customize the Administration and Main menus in Sage CRM. As an example, I'm going to add a custom menu item to the main Sage CRM menu to launch the view to create a new Person record in Sage CRM.
|
-
|
On the last Sage CRM project I worked on, I ran across a little issue with the CRM interface which was causing me a bit of a headache. I was working with a couple of screens I had defined for a custom entity. These screens were similar, so I was doing a lot of comparing one screen to another. Every once and a while, I would notice that the screen contents would disappear from the screen I was reviewing, and I would end up having to rebuild the screen.
|
-
|
In my last blog post, I outlined how to display data from external database in Sage CRM 200. This week, I'm going to do the same thing, but instead of connecting to an external datasource through SageCRM, I'm going to display the data using a custom ASP page.
|
-
|
In this post, I will outline a relatively simply process for displaying data in Sage CRM from an external data source.
|
|  |
|