View more results: All Community | Downloads
  • Blog Post: Using a Create Script to control a Search Screen

    The screen below shows the default company search screen. You can see that a user can search for "Inactive" companies. But... A customer might have the need to stop users from including "Inactive" companies in their searches. The companies should still be accessible in...
  • Blog Post: A Table Level Script to update Opportunities when a Company is Reassigned

    A customer had the requirement that when a company was reassigned to a different account manager, the opportunities that belonged to that company that were still in progress should automatically be reassigned to the new company account manager. This was accomplished using an UpdateRecord event function...
  • Blog Post: Working with Default Company Addresses

    If you need to list company default/main addresses you can link from the Company to the Address table. You don't need to link to the address_link table. The address link table is used to keep details about the alternative addresses that might be stored against a company, e.g. billing and delivery...
  • Blog Post: Connecting to an External ODBC database e.g. Sage 100cloud

    I needed to establish a connection to the Sage 100cloud database to allow me to check details about a customer record within the integrated system. A direct connection to an ODBC database is a very useful way to allow realtime queries to be run against the ERP data from within the Sage CRM interface...
  • Blog Post: Company and Person Workflow Progress with Tracking tab in CRM

    Many thanks must go to a colleague in the UK professional services team for this article. Introduction Customers often request the ability to track Company or Person changes in much the same way that CRM offers with Opportunity and Case entities. As standard, CRM does not offer a CompanyProgress...
  • Blog Post: Add an Additional Address to an Existing Company and Person using SOAP Web Services

    Below is some simple C# code that shows how to add a new Address to an existing company. The address is inserted and linked to the company and the default contact for that company. Notes : The webservice object is called CRMbinding. The Company ID is assumed to be passed from a textBox control...
  • 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: Creating your own Import Scripts using the COM API

    Please read the article " Some thoughts on Importing Data " as background. The previous article discussed the different programming techniques that can be used for importing data into Sage CRM. Web Services COM Based Mechanisms .NET API Direct Data Interaction The COM...
  • Blog Post: CRM.AddContent() & Dummy Field Trick

    I thought I had written about this trick before but it appears not! A customer needed a technique to allow a chart to be displayed at the top of the company screen. This is a bit like the PipeLineGraphic of the OpportunityList or CaseList system screens. The way this has been added is really...
  • Blog Post: Interacting Table Level Scripts: A Chain Reaction

    Consider this scenario. There is an UpdateRecord() event function in a TLS on the Company. When the Company assigned user is changed (comp_primaryuserid) then all the 'In Progress' opportunities belonging to that company are reassigned to the new company account manager (oppo_assigneduserid...
  • Blog Post: Creating Complex Screens using the COM based ASP API

    I have blogged previously on creating Multi block screens based on a single record. A prime example of that would be where you need to design a page for a new entity that include both a detailbox and a webpicker. I would now like to consider a Complex screen where the ASP page offers the user the...
  • Blog Post: Creating a Codeless Extra Entry Tab for a System Entity using Runblock.

    A customer had the requirement to add a new tab option to the company tabs next to the summary tab option. The tab would contain additional fields that have been added to the company table. In addition the tab and the fields should only be available when the company type is 'customer'. ...
  • Media: Partial Rebuild of Company Quicklook Screen using ASP API

    Partial Rebuild of the Company Quicklook page.
  • 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...
  • Blog Post: Calling Workflow in an ASP Summary Page

    This is article is based on a customer need to display workflow buttons in a an ASP page that handles company records. Below you can see that I have created a partial rebuild of the company summary screen. Since this example is based on the Company Summary screen there are a few steps that must...
  • Media: Component: Company Workflow Example (Sage CRM 2018)

    This component when installed will implement a new Company Workflow. This has been tested with Sage CRM 2018 R1. It gives examples of the following business rules and techniques: 1) Changes to comp_slaid will be recorded as a note record. 2) Changes to the comp_slaid can only be made once a communication...
  • Media: Component: Company PeopleList Rebuild (Sage CRM 2018)

    This component will add an new version of the PeopleList within the Company tab menu. This will allow a user to search for a contacts within a company and be able to filter by the person's gender,status etc. The list page has been built using the .NET API ListPage specialised class. A new screen...
  • Media: Component: Import Quicklook DLL (Sage CRM 2018)

    This component will install a new version of the company quicklook page. This has been built using the .NET API. This is compatible with all supported versions of Sage CRM. A file quicklook.dll will be copied into the applications customdotnet folder on the server. A new tab will be added to the company...
  • Media: Component: Add Company Tab Assistant (Sage CRM 2018)

    This component allows you to enter the name of an existing view. It will then create a new custom list based on the view and will change the company tabs group to allow the list to be called from the company context. You will need to enter the name of an existing table - a view based on that table view...