Browse By Tags

  • 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: 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: 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: 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: 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: Converting default ntext fields from an old install of CRM to nvarchar(max)

    This is a SQL script that will solve the problem associated with on-premise accounts that still have some ntext fields in their database from older versions of CRM. The ntext fields do not allow some of the actions that are used in the views of CRM, DISTINCT being an example of one of these commands...