Known issues and limitations

When you right-click a highlighted misspelled word in the built-in email editor, the shortcut menu that opens does not provide a list of suggestions to correct the word. This issue occurs in the Google Chrome, Microsoft Edge, and Mozilla Firebox web browsers and is caused by a third-party component called CKEditor.

WORKAROUND 1

Hold down Ctrl and right-click the misspelled word to display a list of suggestions.

WORKAROUND 2

Install and use a spellchecker extension for your web browser such as LanguageTool.

When you use the built-in email editor to insert an inline image into the email body by selecting Paste in a shortcut menu, a message appears stating that your web browser does not support this functionality and that you should use the Ctrl+V keys instead. But pressing the Ctrl+V keys also fails to insert the image.

WORKAROUND

Below the email editor box, browse for and select a local image file. Select Upload inline image.

When using the RESTful API, you may observe the following issues.

Issue 1: Even though your request sent to the RESTful API uses the HTTPS protocol, the URLs of records returned by the API use HTTP.

Issue 2: The base URL of the records returned by the API may be different from the one you used in your request. For example, the base URL in your request may contain the fully qualified domain name (FQDN) of the Sage CRM server but the base URL of the returned records has the local server name instead.

REASON

Issue 1: This is by design. The RESTful API always uses HTTP in the URLs of returned records.

Issue 2: To form the URLs of returned records, the RESTful API uses the server name stored the Parm_Value column of the Custom_SysParams database table. However, this column can store several names for your Sage CRM server, for example, its local name and FQDN separated by a semicolon:

myserver;myservername.mydomain.com

The RESTful API always uses the first server name stored in this column.

WORKAROUND FOR ISSUE 2

Change the order of the server names stored in the Parm_Value column of the Sage CRM database, so that the FQDN of your server comes first.

1. See the server names stored in the Parm_Value column:

   SELECT Parm_Value from Custom_SysParams where Parm_Name='ServerNames'

2. Back up the Sage CRM database.

3. Run a SQL query to change the order of the server names, for example: 

   UPDATE Custom_SysParams SET Parm_Value = 'myservername.mydomain.com;myserver' WHERE Parm_Name = 'ServerNames'

RESTful API performance may be slow because of the below issue.

Any API call sent to
http://{server name or IP}/sdata/{installName}j/
sagecrm2/-/{resource}
is redirected by IIS to
http://localhost:{port number}/{installName}j/
sagecrm2/-/{resource}.

As a result, the response from the RESTful API contains a JSESSIONID cookie with the incorrect path:
Path=/{installName}j instead of Path=/sdata/{installName}j

Because of the incorrect path, the browser does not register the cookie. This causes Sage CRM to create a new session with a new JSESSIONID cookie.

WORKAROUND

Create an outbound rewrite rule in IIS to change the cookie path in responses from Path=/{installName}j to Path=/sdata/{installName}j.

Example:

<outboundRules>
  ...
  <rule name="Change Set-Cookie crmj HTTP" enabled="true">
    <match serverVariable="RESPONSE_Set-Cookie" 
    pattern="^JSESSIONID=([^;]+); Path=\/crmj;" />
    <action type="Rewrite" value="JSESSIONID={R:1}; 
    Path=/sdata/crmj; HttpOnly;" />
    <conditions>
      <add input="{SERVER_PORT_SECURE}" pattern="0" />
    </conditions>
  </rule>
  ...
</outboundRules>

This example uses crm as the install name.

For more information, see Creating Outbound Rules for URL Rewrite Module in the Microsoft documentation.

In Postman, when you use wildcard characters (%) in a GET request to return specific records, you receive unexpected results.

For example, the following request returns all companies instead of just the companies whose name contains Gate:

GET http://SageCrmServer/sdata/crmj/sagecrm2/-/
Company?where=comp_name like '%Gate%'

This issue is caused by the way Postman processes certain characters. In the past, Postman provided a setting named Use next generation URL processing. By disabling this setting, you could make the wildcard characters work. However, this setting has been discontinued in the recent Postman releases.

WORKAROUND 1

Use URL encoding (%25) to encode the wildcard characters (%) in your request, for example:

GET http://SageCrmServer/sdata/crmj/sagecrm2/-/
Company?where=comp_name like '%25Gate%25'

WORKAROUND 2

Use an alternative client to test the RESTful API, such as SoapUI or ReadyAPI.

When you select the cross icon (x) on a tag to remove it from a record, in some browsers the tag name may disappear from the list before you confirm its removal in the dialog that opens.

WORKAROUND

Ignore this behavior. A tag is not removed until you confirm its removal.