SugarChimp

Hi Vladimir,

Thanks for reaching out. This file is intentionally empty so you can disregard these notices.

Thanks, Heidi

Good afternoon,

The problem is that this definite file generates in CRM repository this file: /custom/Extension/application/Ext/TableDictionary/sugarchimpactivity_.php And this file brakes most of relationships we have in our system. Cache doesn't include a lot of relationships we had before installing SugarChimp. Once we delete /custom/Extension/application/Ext/TableDictionary/sugarchimpactivity_.php file and perform repair - everything is ok with relationships - cache is restored.

Regards, Vladimir.

Hi Vladimir,

Thanks for this response. This is a legacy file that's required for those who had a prior version of SugarChimp installed, so unfortunately we don't have the option of removing it. This issue should only occur when you install or update to a later version of SugarChimp, though it sounds like you are comfortable deleting that file and repairing.

I would love to pass some more insight on to our developer on this. Can you tell me more about how this file is affecting the cache or if you experienced any other symptoms of problematic behavior regarding this file?

Thanks, Heidi

Good afternoon,

I would love to pass some more insight on to our developer on this. Can you tell me more about how this file is affecting the cache or if you experienced any other symptoms of problematic behavior regarding this file? 1. After SugarChimp installation and Repair and Rebuild - the size of Relationship cache file reduces up to 50%... 2. Repair and Rebuild doesn't help, cache remains the same 3. Delete this file /custom/Extension/application/Ext/TableDictionary/sugarchimpactivity_.php 4. New Repair and Rebuild restores Relationships cache up to 100% It looks like that file name sugarchimpactivity_.php in some manner blocks relationship cache building...

Best regards, Vladimir.

Hi Vladimir,

Thanks for passing that along. I've sent this insight to our developer who will attempt to replicate it on our end and work to resolve it in a future release. Once resolved, I'll follow up again and let you know.

Thanks! Heidi