View more results: All Community | Partner Community
  • Blog Post: Adding a new Panel to a Summary screen e.g. Company Summary

    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 of this is discussed in the article " Changing a Summary Screen (e.g. Company Summary Screen...
  • Blog Post: Controlling Top Content

    Above is a screen shot that shows a default opportunity summary page. At the top of the page is the frame that contains the TopContent information. Sometimes this is called the context information. In this screen the TopContent brings in data from the Opportunity, the Company and the Person entities...
  • Blog Post: Reports, Saved Searches and Groups

    I hope in this article to explain the meta definition of the following structures: Standard Reports Saved Searches Groups (Target Lists) These features/structures in Sage CRM all use the Reports tables: custom_reportbands custom_reportcharts custom_reportfavourites custom_reportfields...
  • Blog Post: Step away from the SQL and put your hands where I can see them!

    Amongst Sage CRM developers there are two almost irresistible urges. The first is the itch to write code and try to solve all problems with "if, else" statements. Those of us who are experienced with Sage CRM will eventually learn that much coding can be avoided and we are gradually weaned...
  • Blog Post: The Programmatic Refresh of Meta Data using COM ASP API

    This article will discuss 1) 2 methods to programmatically control the refresh of meta data. 2) The display of the old style workflow configuration screen that governs the marketing workflow Background The existing workflow rules for the marketing tables (Campaigns, Waves and WaveItems) are actually...
  • Blog Post: Adding Derived Fields in Views into Meta Data

    I originally 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 article and will show how meta data definitions of a calculated field can be easily added into Meta...
  • Blog Post: Investigating new and changed metadata structures in an installation of Sage CRM

    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 certain date. The two scripts rely on the fact that Sage CRM is a Meta Data driven application...
  • Blog Post: The Sage CRM .NET API

    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...
  • Blog Post: Using Joins in Web Services

    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 could use the QueryObject to build the exact SQL you need. var mySQL = "SELECT Person.*,...
  • Blog Post: Custom_Edits and Derived Fields Created in Views

    In CRM it is quite common to need to create a view that performs a calculation or derives information to be displayed on screen or in a report. An example of this can be found in the Case management area. For example if you logon to a demo system as Kylie Ward (WardK) and navigate to the My CRM menu...
  • Blog Post: Building Lists without reference to Meta Data in the ASP COM API

    Above is a picture of a new list added into the My CRM area of Sage CRM. The code below shows how a list can be created using the ASP COM API. var intRecordId = CRM.GetContextInfo("user","user_userid"); var Arg = "oppo_assigneduserid="+intRecordId; var myBlock = CRM.GetBlock...
  • Blog Post: What makes an Entity?

    The concept of the Entity is important within Sage CRM and is used through out the system. When dealing with databases and designing applications the term entity can be used to describe anything of significance. This is true for both real and conceptual entities about which the system needs to hold information...
  • Blog Post: Sage CRM and Referential Integrity

    One of the great strengths of Sage CRM is its openness. Its data model is documented and published and available to members of the Developer Program. In some applications relationships between the different entities may be fixed or defined within the database. This is not the case within Sage CRM...
  • Blog Post: Resetting Passwords

    I have had a few emails from different people over the last few weeks asking about code that will allow a system administrator to quickly reset a users password. I created a little ASP page that demonstrates how this can be done. You can develop this idea further by send an email to the user. The...
  • Blog Post: What is a Block in Sage CRM?

    The word Block crops up over 1300 times in the Sage CRM developers guide. The word is actually quite a loose term that is used to name some of the Application Programming Interface (API) objects that can be referenced to extend the system. The API objects are discussed in the Developers guide. Those...
  • Blog Post: Make sure to Refresh Meta Data when Changing SOAP Web Services configuration (Sage CRM 7.1c and earlier)

    I have been updating some Web Services code and was trying my test application against a new install of Sage CRM. I needed to change the setting in Administration -> System -> Web Services from Dropdown fields as strings in WSDL file : No to Dropdown fields as strings in WSDL file...
  • Blog Post: Manage Escalations

    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 of Sage CRM where there are a large number of rules to manage. When working with large number of Escalation...
  • Blog Post: Building a Screen not bound to Meta Data using the ASP COM API

    The code below demonstrates how a page like the Preferences screen can be rebuilt in Sage CRM. This particular screen may be needed to be replaced if the business wishes to offer users only a limited set of preferences that maybe controlled. In the default system the system administrator can either let...
  • Blog Post: More Adventures with the Library

    I have been investigating the list of documents that appears under the Company tab group. This is actually part of a set of investigations into the library entity that I am working on. So there will be a few more blogs about documents and the library in the near future. I wanted to find out how to ensure...
  • Blog Post: Changing the EntryType for Fields in an External Table

    Within Sage CRM it is very easy to link to an external table that exists in another database. For example you may wish to link to a table such as ap_customer or ap_vendor in Sage 100cloud. How the link can be created is described in the article " Connecting to an External ODBC database ". ...
  • Blog Post: How does metadata create a Screen?

    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=1&CLk=T&Key0=8&Key1=43&Key2=57&Key8=46&T=Case We can see that the Action...
  • Blog Post: Building selection lists in ASP pages without reference to Meta Data

    From time to time you will need to build pages that can not directly be based on a Meta data definition of a screen. For example if you need to construct a page that allows cloning of an entity or perhaps interaction with an external system. The CRM objects allow to you to easily build screens and entries...
  • Blog Post: Customizing a Screen

    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 a Case's Summary Screen will look something like this: http://localhost/CRM/eware.dll/Do?SID=198369875659391&Act=281&Mode=1&CLk...
  • Blog Post: Suppressing Display of Duplicate Meeting Records in Company and Person Context

    A component that implements this feature can be found in the download folder " Example components and developer resources ". You will need to be logged on to the community with the correct rights to be able to access this library of resources. The image below shows the default behaviour...
  • Blog Post: Creating a new database connection to Sage Business Cloud Enterprise Management (formerly Sage X3) (Part 2)

    This is the second article in a series that discusses creating a new database connection to the Sage X3 database using the standard Sage CRM features. Sage CRM's screens are defined in Meta Data. The Meta Data is held in tables within Sage CRM and this is key to understanding how new screens...