Customers moving from any version of SedonaOffice before 6.2.0.x will come across the following issues dealing with Monitored By/CS Integration on the site/system. The sections below will go over how to fix those issues.
CS Integration data work needed after the upgrade.
After a customer upgrades to 6.2.0.x, the following scripts will need to be run to make sure they do not get errors.
Steps:
Will need to ask the customer if they are “Live Linked” to any CS companies. (ie. Manitou, CMS, Stages)
If they are live linked, then you will need to determine what CS_Alarm_Company needs to show Active, what Integration_Id needs to be assigned to each Alarm_Company_Code/Id
Depending on the answers above will depend on how the update scripts below will be used
-
This script shows how many accounts are associated with that Alarm_Company_Id
SELECT Alarm_Company_id, Count (*) from AR_Customer_System group by Alarm_Company_Id order by Alarm_Company_id asc
-
This script shows what Alarm_Company_Code goes with which Alarm_Company_Id to see how associated with the Integration_Id
Select * from CS_Alarm_Company
-
This script shows what SS_Integration has for each Integartion_Id and the description
Select * from SS_Integration
-
These scripts are to be used to update CS_Alarm_Company results depending on how the customer is linked to a CS Alarm Company.
** Any Alarm Companies that are not live linked NEED to be assigned to Integration_Id = 1
** Set any CS_Alarm_Company that is not used as Inactive = ‘Y’ so not to accidentally be used
-- // Update CS_Alarm_Company SET Integration_id = 1 where Alarm_Company_id in (1,2)--// Update CS_Alarm_Company SET Inactive = 'Y' where Alarm_Company_id in (2,6,7,8,9)
Example Screenshot of each script:
CS Integration Error Messages and how to fix
Below are the different error messages that CS Integration can receive after the upgrade and how to fix them.
CS Integration Errors:
“This system can only be unlinked or linked to a non-real integration company.”
Customers will get this error when trying to link the system to a different Monitored By/CS Integration company that is different than what the Site is showing.
In version 6.2.x, linking is now done at the system level, not the site. So, no matter how many systems you have on a site you can only link ONE Monitored By/CS Integration company.
The only way to change from one to another is by selecting Not Monitored – Save the record then go back into the system and change to the correct one.
If the system is to have a different company than another system, the customer will have to keep the Monitored By/CS Integration set to Not Monitored and add the other company in the Memo field.
“System is configured as being linked to a CS Integration …..”:
If a customer gets this error message, it could be a real informational message or be part of the issue after upgrading.
If there is not a CS Link and the system is a “live linked” account there must be a link in this field, if there is not then this is a legitimate message.
NOTE: There does not need to be a CS link entered; however, will keep getting the message every time the system or site is opened if there is not a link.
If the system is not “live linked” then need to look at how the CS Alarm Company is associated and may need to run scripts to fix or change to Not Integrated for that Monitored By Company.
