Technical Hints Tips and Tricks that cover customization and development using Sage CRM. API usage and coding are covered.
Browse by Tags
All Tags »
Meta Data (
RSS)
-
|
This article was updated (31st October 2009) to correct links. It is perfectly true that for an early version of 5.8 we managed to generate a malformed WSDL file so that briefly people had to manually...
|
-
|
The links in this article were corrected on 31st October 2009. This option, that is available for an on premise install, is found under Administration -> System -> Database It looks like this feature...
|
-
|
I have added to the resources section two very simple SQL scripts that can be used to help you report what new Meta Data structures have been added to an install of Sage CRM and what has been changed since...
|
-
|
A new example component has been added to the resources section for development partners to download. The purpose of this component is to make the management of escalation rules easier in implementation...
|
-
|
I orginally wrote about creating derived fields in a view in the article " Custom_Edits and Derived Fields Created in Views ". This discussion is a continuation of the ideas expressed in that...
|
-
|
This article has been edited 9th June 2009 to following the coding convention introduced in Sage CRM 6.2. This article will discuss 1) 2 methods to programmatically control the refresh of meta data. 2...
|
-
|
This article has been updated 9th June 2009 to correct formatting and to change the code to use the convention introduced in Sage CRM 6.2. Above is a picture of a new list added into the My CRM area of...
|
-
|
Imagine you need to retrieve information from CRM via the webservices interface; this query should combine data from multiple tables. In the COM API (ASP pages, self service, table level scripts etc) you...
|
-
|
A screen like the company summary screen has a very particular structure because it is partially defined in meta data and partial has its structure hard coded into the system action being called. The detail...
|
-
|
If we consider a screen like the Case Summary screen we can imagine it being built in a series of layers. If we consider the hyperlink http://localhost/CRM/eware.dll/Do?SID=198369875659391&Act=281&Mode...
|
-
|
This article has been updated to correct links I have written about the quirkiness of the Self Service API previously in the article " Self Service Quirks ". It that post I pointed out that the...
|
-
|
This article has been updated to follow the coding convention introduced in Sage CRM 6.2 From time to time you will need to build pages that can not directly be based on a Meta data definition of a screen...
|
-
|
This article has been updated to ensure the code follows the coding convention introduced in Sage CRM 6.2. The code below demonstrates how a page like the Preferences screen can be rebuilt in Sage CRM...
|
-
|
This article has been updated to correct links. A screen is called as a result of a hyperlink. This may be a button click, a call from the recent list or any other selection from the interface. A URL of...
|
-
|
This article has been updated to include new material for Sage CRM 6.2.1. A new component that implements this feature has been added in the resources section. http://dpp.sagecrm.com/files/folders/components...
|
More Posts
Next page »