Sage CRM

 View Only
  • 1.  New and exciting problem with #SageCRM. Client rec

    Posted 04-30-2012 16:41
    New and exciting problem with #SageCRM. Client recently upgraded to v7.1 (same client as my previous post). We resolved the last issue, and now we've got a new one. Searching for company by phone does not work, even though almost every single company has a phone number stored in the database. Doing some research with the client, and we dove into the SQL management studio. Turns out that the company search view is based on a table dbo.CRMEmailPhoneData, but the table has hardly any data. The table dbo.Phone has all the data from the prior version, but is not used in the search view. Thinking there may be a #bug of some sort in the upgrade procedures, or maybe I missed something in the instructions.


  • 2.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 04-30-2012 16:56
    This is a known upgrade bug. Can't believe Sage hasn't fixed it yet. I don't know the solution off the top of my head but our team has run into it on many CRM 7.1 upgrades. Let me check ...


  • 3.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 04-30-2012 17:01
    Thanks, @PeterWolf. At least my client is understanding. They do some programming for their product, and they understand how hard it is to make something right when you only have a three-man programming shop....


  • 4.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 04-30-2012 17:47
    And something I stumbled on tonight. Funny how this happens sometimes: http://chrisjhorn.wordpress.com/2010/05/11/why-is-software-engineering-so-hard/.


  • 5.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 05-01-2012 08:51
    I re-sent the request to my team. Haven't heard back yet... I guess everyone is too busy on client projects and they are ignoring me?


  • 6.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 05-01-2012 09:42
    Business would be a lot easier if we didn't have to deal with employees and customers. :-)


  • 7.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 05-01-2012 11:53
    Or they're just ignoring you.


  • 8.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 05-01-2012 14:06
    Call back from Sage: there is an issue, and there is a Stored Procedure (under Programmability in SQL Server Management Studio) called ""Populate_dbo_CRMEmailPhoneData"" (or something like that). We had to split the SQL into the ""DELETE"" statement and ""UPDATE"" statement to make it work for us, but I wasn't paying a lot of attention to the SQL code. As always, make a backup first. #solution #solved


  • 9.  RE: New and exciting problem with #SageCRM. Client rec

    Posted 05-02-2012 11:39
    Here's the word back from my guys: purge all deleted records from phone and email tables prior to upgrading. That seems to do the trick in most cases.