J jleinbac Guest Feb 24, 2014 #1 Further investigation shows that the issue was caused by enabling Historical Trending on objects in Salesforce. This issue has been resolved. Continue reading...
Further investigation shows that the issue was caused by enabling Historical Trending on objects in Salesforce. This issue has been resolved. Continue reading...