Sage 200(UK): Difference between revisions
From Accelerator for SageCRM
No edit summary |
No edit summary |
||
Line 39: | Line 39: | ||
*Due to how Accelerator creates and updates a person record the line | *Due to how Accelerator creates and updates a person record the line | ||
eWare.ExecSql('UPDATE Person SET Pers_AccountId=' + accountID + ' WHERE Pers_PersonId=' + personID); | eWare.ExecSql('UPDATE Person SET Pers_AccountId=' + accountID + ' WHERE Pers_PersonId=' + personID); | ||
causes an SQL Lock | causes an SQL Lock that times out. We don't need this to run as we look after this data. |
Revision as of 16:49, 17 October 2014
Sage 200 UK edition installs specific tables into CRM which require an extra option being turned on
To turn on 200 integration need to change setting (web.config)
<add key="UsesSage200UK" value="Y" />
- The install will also provide this option.
- There is also an SQL script provided which is needed to be run to create the stored procedures used in the integration
Finally we must create a new field on person (we created a checkbox called 'Pers_ct_accelcreated')
The we add this to the screen 'PersonOfficeIntNew' and we set the create script to be
DefaultValue='Y'; Hidden=true;
We then update the Table level script 'TLS_HideAccount_Person'
Search for the text
// Set the Account ID (only ExecSql works). eWare.ExecSql('UPDATE Person SET Pers_AccountId=' + accountID + ' WHERE Pers_PersonId=' + personID);
and update this to be
if (Values('Pers_ct_accelcreated')!='Y') { // Set the Account ID (only ExecSql works). eWare.ExecSql('UPDATE Person SET Pers_AccountId=' + accountID + ' WHERE Pers_PersonId=' + personID); }
- Due to how Accelerator creates and updates a person record the line
eWare.ExecSql('UPDATE Person SET Pers_AccountId=' + accountID + ' WHERE Pers_PersonId=' + personID);
causes an SQL Lock that times out. We don't need this to run as we look after this data.