Browse By Tags
Home
»
All Tags
»
ASP
»
.NET API
»
COM
buttons
Code Snippets
custom_tables
Data Model
eWareQuery Object
Import
Integration Options
Javascript
Meta Data
Outlook Integration
PipeLineGraphic
PsuedoURL
Query
Record Object
redirect
Sage CRM
SDK
Search Screen
Security
SQL
StoredProc
Web Services
Blog Post:
Discovering Data Relationships in Code
Jeff Richards
You may have a business requirement to cascade a change through the child records of a company. I have discussed previously how a table level script can be used to update all opportunities if the company is reassigned to a new account manager. See the article " A Table Level Script to update Opportunities...
on
13 Sep 2010
Blog Post:
Integration with External Systems and the Synchronization of Application Data
Jeff Richards
Introduction Sage CRM is integration-ready straight out of the box. It can integrate quickly with Sage BMS products, as well as other external applications through secure, standards-based web services and APIs. In this article I want to discuss the different approaches that can be taken by a developer...
on
12 Jan 2017
Blog Post:
Adding a Button that Passes Contextual Information to an External Webpage
Jeff Richards
You can add a button In a custom ASP page In a the code of a .NET assembly In a an existing system screen Buttons in an ASP Page If this is in an ASP page then the code for a simple button to call an external ASP page looks like var strCallASPButton = CRM.Button("ASP"...
on
16 Sep 2011
Blog Post:
Building a Simple Quick Search Page
Jeff Richards
Entities such as Case and Solution use a reference field as an alternative key. This is the 'ticket' number (case_referenceid, soln_referenceid) that is used as a public and convienent way of identifying each record. In the default demo system the fields case_referenceid and soln_referenceid...
on
5 Mar 2009
Blog Post:
The Sage CRM .NET API
Jeff Richards
The diagram below shows the general architecture of Sage CRM. Here you can see very clearly that the .NET API is an alternative and NOT a replacement for the COM API which is currently used to build application extensions with ASP pages. Both the .NET API and the COM ASP API use the Meta...
on
28 Sep 2007
Blog Post:
Some thoughts on Importing Data
Jeff Richards
I have written several articles in the past about the importation of data into Sage CRM. This article then is a 'header' record that attempts to bring these different thoughts together. It is certainly not unusual for a partner to occasionally need to design a custom import mechanism into...
on
31 Dec 2008
Blog Post:
Creating a PipeLineGraphic in an application extension using COM API ASP
Jeff Richards
I have discussed in a previous article how customization can be carried out on a PipeLineGraphic chart used in a system built page, for example on the Opportunity List page in the My CRM tab area. The PipeLineGraphic block is available within the COM and .NET APIs but it has not always been straight...
on
31 Dec 2007
Blog Post:
Redirecting from a COM ASP page to a .NET assembly
Jeff Richards
You may have a need to redirect from a custom page written using the COM ASP API to a .NET assembly. I have written about redirecting from COM ASP page before in the article " Redirecting to an ASPX (ASP .NET) Page from a Classic COM ASP page " The code below shows how a URL for the redirect...
on
8 Sep 2011