Browse By Tags
Home
»
All Tags
»
Fields
»
COM
ASP
buttons
Code Snippets
Columns
Company
create script
dates
Drop Down Lists
Entry Screen
EntryTypes
ewaress.js
Graphs
GridColumns
Javascript
JScript
List Block
List Page
Meta Data
Multiple Blocks
Search Screen
Search Select Advanced
Security
Self Service
Table Level scripts
Workflow
Blog Post:
Self Service Workarounds
Jeff Richards
If you have been working with Self Service then you know that certain field entrytypes are not rendered in the same way in Self Service screens as they are in the main application extension ASP pages. These oddly behaving fields or entrytypes include Date, DateTime and Search Select Advanced fields...
on
13 Mar 2009
Blog Post:
Useful Date Functions
Jeff Richards
Occasionally you will need to fetch a date from either the CRM database or perhaps from an external system that is then needs to be formatted so it looks like a CRM date. All users are able to set their date preferences. The are other articles that discuss handling dates Add/Subtract...
on
10 Jul 2009
Blog Post:
More about Using CRM security in ASP pages
Jeff Richards
I have previously discussed that access to buttons can be controlled by the 4 & 5 parameter of the CRM.Button() method used in Classic ASP. The entity referenced in the 4th param has to be an entity normally covered by security. The example covered in the previous example discusses whether or...
on
10 Feb 2009
Blog Post:
Manage Escalations
Jeff Richards
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...
on
3 Jul 2009
Blog Post:
Field Level Security and Create Scripts
Jeff Richards
The control of field level security can be found against each field listed under the Field tab in the customization area. Administration | Customization | TableName We know from the documentation that the field security interface provides a simple code-free approach for administrators to define how users...
on
21 Dec 2007
Blog Post:
Building selection lists in ASP pages without reference to Meta Data
Jeff Richards
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...
on
13 Mar 2009
Blog Post:
Setting screen properties within a multiblock ASP page using the COM API
Jeff Richards
This COM API trick for ASP based Application Extensions shows how you can create a screen with 2 (or more) blocks where one of the blocks remains in view mode regardless of the value of CRM.Mode. It is a very simple approach and all you have to do is get hold of the block that you wish to be read only...
on
28 Nov 2007
Blog Post:
Sage CRM EntryTypes used in the COM ASP API
Jeff Richards
I have covered manually building screens, that is without using existing Screen or List meta data definitions in earlier posts. These contain example code that uses the following basic struture of code to build the fields. var customTextEntryBlock = CRM.GetBlock("Entry"); with (customTextEntryBlock...
on
13 Mar 2009
Blog Post:
Building a Search Select Advanced Field in ASP
Jeff Richards
I have covered the EntryTypes used in CRM in an earlier article, " Sage CRM EntryTypes used in the COM ASP API ". Below is a simple example showing how to create a Search Select Advanced in an ASP page. var myBlock = CRM.GetBlock("opportunitydetailbox"); var personidBlock = CRM...
on
13 Mar 2009
Blog Post:
CRM.AddContent() & Dummy Field Trick
Jeff Richards
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...
on
28 May 2010
Blog Post:
A Universal "Go Back" button in Workflow
Jeff Richards
The requirement to allow the user to fall back to an earlier point in the workflow is usually handled by looping. We can see from the diagram below how a workflow can allow a user to drop back and repeat or cycle through certain workflow states again and again. But what if we need to have a workflow...
on
1 Nov 2009