Visit Sage CRM Main Website
About Sage CRM
Browse By Tags
Drop Down Lists
Table Level scripts
How to display an oppo_opportunityid or another primary key in lists and reports.
Once you have been working with Sage CRM for a little while you will notice that the primary keys (unique ID fields) have been suppressed from the interface. By that, I mean that you can't refer to them directly in Lists and Screens. This is normally fine as the keys job is only to allow Sage...
9 Sep 2016
Who's been looking at my data? Recording access to Company and Person screens
I have discussed creating logs and audit trails of changes to data in previous articles. See Using a Table Level Script to Track Changes to Data Made by Users. Validation rules don't always mean "Stop!" But many customers have the much more straight forward business need...
13 Jul 2010
Write to the CRM logs in a server-side script
Sage CRM Team
If you are developing a server-side script such as a Create Script, Validate Script or Table Level Script, it is often useful to write debugging information to a log. Jeff has blogged about a technique for doing this using the Scripting.FileSystemObject. I'd like to share with you a very simple...
1 Oct 2009
Using SearchSQL to limit data returned by selection lists
In the screen shot below we can see the demo user "Susan Maye" is limited to assigned the new opportunity to only people in the "Direct Sales" team. This has been accomplished by using the property of the field (a.k.a entryblock) called SearchSQL. The SearchSQL property is discussed...
27 Jan 2008
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...
3 Jul 2009
© The Sage Group plc 2019
All Rights Reserved