Browse By Tags
Home
»
All Tags
»
Javascript
7.1
7.2
7.3
Any DB
API
article
ASP
buttons
Client Side
Client Side API
clientside
Columns
COM
CRM Standalone Install
Customisation
customization
English
Interactive Dashboard
JackAllan
JQuery
Known Bug
Lists
Sage CRM 2017
Table Level scripts
Workflow
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:
Example Code to Generate a Pseudo-Random Password
Jeff Richards
A Customer had a need as part of a Case Workflow to generate a Self Service username and password for their contacts. They were using an ASP page to do this and asked whether I had any code to generate a password for Self Service. This is a simple little script and you may find this useful for your...
on
14 Jan 2013
Blog Post:
The Client Side CurrentUser object
Jeff Richards
In every screen (entrygroup) where you can add javascript (<script>) into the custom content box you can reference the clientside CurrentUser object. You can see that this has been used in several articles in the blogs such as " Controlling Buttons using Client Side code " And other...
on
2 Sep 2011
Blog Post:
Javascript Coding Made Easier with a Development Studio - Jet Brains Webstorm
Kannan Srinivasan
I see most of us in the developer community wanting to develop Sage CRM Client Side customizations via Javascript, but we when we use Visual Studio may not have great flexibility in writing client side code, This studio i.e. Web Storm helps you write Javascript based code for both HTML & HTML 5 with...
on
13 Aug 2012
Blog Post:
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...
on
1 Oct 2009
Blog Post:
How to filter a pipeline object based on filter screen values
Sage CRM Team
We know that a LIST block can be filtered based on a standard filter screen block via var filter = eWare.GetBlock("MyFilterBoxName"); var list = eWare.GetBlock("MyListName"); list.ArgObj = filter; Can we filter a pipeline object in a similar fashion? Unfortunately you cannot...
on
24 Apr 2009
Blog Post:
The Client Side API
Jeff Richards
This is a simplified and specialised set of code libraries that will allow easy screen customizations. The API is based on the JQuery syntax although I must stress that knowledge of JQuery is not needed in order to use the API. The API is included as part of the full product development cycle and...
on
28 Mar 2013
Blog Post:
Adding a Button that Passes Contextual Information to an External Webpage
Jeff Richards
You can add a button In a custom ASP page In a the code of a .NET assembly In a an existing system screen Buttons in an ASP Page If this is in an ASP page then the code for a simple button to call an external ASP page looks like var strCallASPButton = CRM.Button("ASP"...
on
16 Sep 2011
Blog Post:
Filing e-mails against custom entities
Sage CRM Team
* The code in this article has been updated to fix a bug that caused it not to work for any entity that did not have a prefix that matched the entity name * A while back Jeff Richards wrote a blog post about how to add a button to the communications tab of a custom entity to send an e-mail just like...
on
23 Jun 2009
Blog Post:
Defining Namespace References
Jeff Richards
In a previous article " Script Libraries: Reusing Client Side Code Between Screens " I discussed how Sage CRM will automatically add any JavaScript file that you add to the custom folder into the header of every page produced by the system. It is a good idea when adding script libraries...
on
25 Jun 2013
Blog Post:
Binding Client Side Script to the onLoad event using crm.ready()
Jeff Richards
Sage CRM has a Client Side method crm.ready() which is used to execute scripts once the page is loaded. We do not have to worry whether the browser is Chrome or Internet Explorer. The crm.ready() method will take the browser version into account and add the function we pass to it in the correct way...
on
11 Jun 2013
Blog Post:
Script Libraries: Reusing Client Side Code Between Screens
Jeff Richards
It has always been possible in Sage CRM to share client side code between screens. In Sage CRM we could do this by using a shared external script library. For example if we wanted a set of business rules to be available in both the PersonBoxLong screen and the PersonBoxDedupe screen then we could...
on
18 Jun 2013
Blog Post:
Using Custom Content Script to Change the Properties of a Field based on Displayed Value (before Sage CRM v7.2)
Jeff Richards
Note: This type of customization has become easier in Sage CRM v7.2 using the new Client Side API). The fields in screens are output with clear 'IDs' that allow the control of the field caption and data to be very easy. The HTML that makes up the display of a field like the comp_name...
on
28 May 2010
Blog Post:
Controlling the RecentList using Client Side Code
Jeff Richards
The GoRecent function is held in Sage CRM in an external file which is included in every page. Sage CRM Code Example <script> function doCode() { SageCRM.webMenu.GoRecent('C'); } </script>
on
2 Jul 2013
Blog Post:
Changing Search Select Advanced display fields
Sage CRM Team
CRM allows you to change the display fields used in an Search Select Advanced (SSA) field but it does not give you control over the order of the fields displayed. The following function, placed in the custom content of the screen, will allow you to change the order of the display fields: <script>...
on
6 Apr 2009
Blog Post:
Modify field on another table in a workflow action
Sage CRM Team
When choosing a field for the Display Field For Amendment action, you can select fields from the view that are not on the table the rule is based on. For example you can select the comp_primaryuserid if you use the vSummaryOpportunity view to base your rule on. However this will not work by design: You...
on
24 Apr 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:
Conditionally send e-mail on entity creation
Sage CRM Team
It is common to have CRM send out an e-mail on the creation of a new entity. For example you may have an e-mail sent to the assigned user on a new Opportunity notifying them that a the Opportunity has been created and that it is assigned to them. This is achieved by putting a Send E-mail action on the...
on
24 Apr 2009
Blog Post:
Using Chrome to help write Client Side Scripts
Jeff Richards
What I find is so useful about the Chrome developer console is that it lets you edit JavaScript code on the fly and so is a very good way of starting to evolve a business rule that needs to be written in the Custom Content field or even an onChange script. In the image above you can see how I have...
on
13 May 2013
Blog Post:
Using the Clientside API to control Tabs
Jeff Richards
Consider the following business rule. "A customer has a requirement that the Case Tab in the company screen should only display when the Company has an agreed service level agreement and the user accessing the screen is in the 'Customer Service' team." This is a business rule...
on
23 Jul 2013
Blog Post:
Detecting Screen Mode in the Client Side API
Jeff Richards
Sage CRM Screens can exist in different ‘Modes’. The basic two modes that we have to worry about in Client Side code are View and Edit. We can use the fact that in Sage CRM <INPUT> HTML tags are named and have an ID with same name as the physical field in the database. e.g. <input...
on
21 Oct 2013
Wiki Page:
608-16539 - Unknown scripting language 'JavaScript' error in Interactive Dashboard
Support team
Summary: An error stating that JavaScript is an unknown scripting language may appear when navigating to the Interactive Dashboard. Resolution: On the server, go to Start -> Run . Type CMD then hit Return . A command prompt window will open. In the window that's displayed, enter the following...
on
16 Apr 2014
Wiki Page:
492-16626 - Script error when opening custom url in a new window
Support team
Summary: Opening a custom URL in a new window may result in a script error in v7.2. Symptoms: A custom URL can be added to the main Find menu by nanvigating to Administration -> Advanced Customisation -> System Menus ,and selecting the Find menu option. In order to have the URL open a website in...
on
16 Apr 2014
Wiki Page:
492-16866 - Setting screen focus at the top of a list
Support team
Summary: When using a low screen resolution (800x600) and a gridsize higher than 10 (i.e. 25), the focus for UserContactList (MyCRM -> Contacts) will scroll down to the last row of the grid. Symptoms: The customer wanted the focus set to the top of the grid. Work around / Resolution: There’s...
on
16 Apr 2014
Blog Post:
Control of Grids, Lists and Columns Using the Client Side API
Jeff Richards
The Client Side API contains methods that make it much easier to select rows, columns and individual cells for manipulation. Properties can be set, new data displayed in tool tips and the style of each cell can be changed. The documentation contains a good discussion of how to use the API. You can...
on
13 Nov 2013
>