Browse By Tags

  • Blog Post: Building Cross Database Views for Reporting

    You may need to reference data held outside of Sage CRM and within another application's database for a variety of business requirements including Reporting Graphing Reports within CRM are based on views and so if the SQL within a view can provide a way of accessing data...
  • Blog Post: Reports and Graphs using Key Attribute Data

    Reports and Report Charts can only be built from views. So If we want to create a Report Chart that uses Key Attribute Data then we must first create the view. The structure of the tables that holds the key attribute data is complex and trying to work this out on our own to build a view would be a deeply...
  • Blog Post: What Reports have Charts?

    A customer had a requirement to see which reports had charts associated with them so they could consider them as Chart Gadgets in their Interactive Dashboard. It is not immediately clear from the standard report screen which reports might have a Pie chart or HBar associated with them: To allow...
  • Blog Post: Creating Groups on Custom Entities in Sage CRM

    I have created a new custom entity called 'Project' using the Advanced Customization Wizard (aka Entity Wizard, Main Entity Wizard). The requirement: The requirement was to be able to use data from the project table in groups used for outbound emails, and within the Interactive Dashboard...
  • Blog Post: Tips for Building Views: A round up of articles on views.

    The following is a survey of all the different articles that have discussed creating and editing views within Sage CRM. Understanding SQL views is essential as they under pin just about every feature within Sage CRM and completely determine what can or can't be done in Reports, Marketing Groups,...
  • Blog Post: Creating Interactive Dashboard List Gadgets for Custom Entities

    List Gadgets derive their data from 4 different types of data source Saved Searches Advanced Finds Reports Groups When a custom entity is added to Sage CRM using the Advanced Customization Wizard (Entity Wizard) only the table is created. The default behaviour associated with...
  • Blog Post: Creating Groups on External Tables in Sage CRM (E.g. Sage accounting systems)

    The requirement: The requirement was to be able to use data from an external table in a group definition. This will allow data from a Sage accounting system to be used to build groups of Person and Companies that can then be used for outbound emails, and within the Interactive Dashboard as data sources...
  • Blog Post: Understanding the CRMEmailPhoneData table

    If you have spent time looking at the way in which views are constructed in Sage CRM then you may have found the CRMEmailPhoneData table referenced and wondered what is the table's purpose. I asked a colleague in our development team for some help in explaining the table and the following information...
  • Blog Post: Why do Phone numbers appear in the Company and Person screens when they are stored in the Phone table?

    This is a follow up to the article I wrote previously called " Understanding the CRMEmailPhoneData table ". That article explained that the CRMEmailPhoneData is a utility table and that it's job is to speed up reports. It holds a row for each company or person with that company or persons...
  • Blog Post: Hold the Phone! A round up of articles that discuss Phone Numbers and Email addresses in Sage CRM

    In Sage CRM development around phone numbers and email addresses needs careful thought. This is because Sage CRM "entities" can be complex. For example the information for a Company consists of a company record, a default person record and a default address. Both the company and the default...