Summary:

A user creates a new company in CRM and sends this compnay to X3 using the "Post to X3" function.

Now when a user navigates to a X3 tab eg "X3 Customer" for this company the tab is bigger than that of a standard CRM tab eg "Summary" (see screenshots below).

Symptoms:

Standard CRM Tabs:

Description

 

X3 tabs in CRM:

Description 


Resolution:

To resolve this issue navigate to   C:\Program Files (x86)\Sage\CRM\CRM\WWWRoot\CustomPages\Enbu\eware.asp
The issue is on line 115 and 117:

if (sInstallName!=""){
                            Response.Write(“<HTML><HEAD><META http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">");
                            //Response.Write('<script type="text/javascript" src= "../jquery-1.4.4.min.js" ></script>');
                } else {
                            Response.Write("<HTML><HEAD><LINK REL=\"stylesheet\" HREF=\"eware.css\"><META http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">");
                }
                        Body="<BODY>";
                        EndBody="</BODY></HTML>";

The following is missing for the above code: <!DOCTYPE html>
If you edit the above code to include this it should work as expected (see highlighted below).

if (sInstallName!=""){
                            Response.Write("<!DOCTYPE html><HTML><HEAD><META http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">");
                            //Response.Write('<script type="text/javascript" src= "../jquery-1.4.4.min.js" ></script>');
                } else {
                            Response.Write("<!DOCTYPE html><HTML><HEAD><LINK REL=\"stylesheet\" HREF=\"eware.css\"><META http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\">");
                }
                        Body="<BODY>";
                        EndBody="</BODY></HTML>";


Status:

This issue will be resolved in a future release of the Sage X3 Connector but this will resolve the issue for new installs only.
To resolve this issue for existing installs the resolution above must be implemented.