Browse By Tags

  • Blog Post: Example of a Complex Screen editing multiple records in ASP

    I have written before about the creation of a complex screen where the ASP page offers the user the ability to edit two records at the same time. See: https://community.sagecrm.com/blogs/hints_tips_and_tricks/archive/2007/10/01/creating-complex-screens-using-the-com-based-asp-api.aspx This code...
  • Blog Post: Creating and controlling Edit Pages in Self Service

    Below is a very simple example of a self service page that allows a case belonging to an authenticated visitor to be edited. The ASP code is found below. The code is comment and discussed. <%@CodePage=65001 Language=JavaScript %> <!-- #include file ="ewaress.js" -->...
  • 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: AddContent() and GetPage() versus GetTabs() and Execute() in COM ASP API

    You can render a page using var myBlock = CRM.GetBlock("opportunitylist"); Response.Write(CRM.GetTabs()); Response.Write(myBlock.Execute()); The important thing here is that the Execute() method of the block generates the HTML that is to be returned to the page. A page generated this way...
  • Blog Post: How to Create a Secondary Entity for a new Custom Primary Entity

    This article shows the steps that I went through to create a secondary entity that is a child of a Custom Primary Entity. The business scenario that I imagined was that I had a new Primary Entity called Project that was created using the Advanced Customization Wizard. I needed to create a secondary...
  • Blog Post: Basic Code Structure of an Edit Page

    We should now consider the creation of an edit screen for a Record using an ASP page. The structure is simpler. var myBlock = eWare.GetBlock('OpportunityDetailBox'); var myRecordId = eWare.GetContextInfo('Opportunity','oppo_opportunityid'); //var myRecordId = Request.QueryString...
  • 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...