+ Start a Discussion
otivbotivb 

Dependent class is invalid and needs recompilation error during deployment following FinancialForce PSA Upgrade.

Following a recent upgrade to our FinancialForce PSA System we are no longer able to deploy into production certain APEX Classes (message below) Any of our test classes that creat a Contact Record are experiencing this issue. We tried Setup > APEX Classes > Compile All Classes and Setup > APEX Triggers > Compile All Triggers without any success. PSA has not been able to assist and have indicated that the issue is related to the following: https://success.salesforce.com/issues_view?id=a1p3A000000mCXpQAM

As PSA is a managed package we have absolutley no control over the trigger that is causin this. Any help would be appreciated?

=========
System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, pse.ContactTrigger: execution of BeforeInsert caused by: line 48, column 22: Dependent class is invalid and needs recompilation: Class pse.SearchResourcesGeoLocationManager : Dependent class is invalid and needs recompilation: Class pse.MockHttpResponseGeneratorForGeolocation : Dependent class is invalid and needs recompilation: Class pse.ExternalAPICredentialService : Dependent class is invalid and needs recompilation: Class pse.Application : Dependent class is invalid and needs recompilation: Class pse.TimecardHeaderSelector : Variable does not exist: LastReferencedDate: [] 
Stack Trace: Class.RWW_TestHelper.getContact: line 143, column 1 Class.RWW_TestHelperTest.testGetContact: line 28, column 1
=======


 
Rob Scott 26Rob Scott 26
We are running into this as well. Did you get this resolved?
otivbotivb
The issue is still not reolved (coming up to a month). FinancialForce and Salesforce R&D are still working on this issue. I recommend you open a case with FinancialForce, they will escalate the issue to salesforce.
Charles Hill 18Charles Hill 18
This is still an issue.  Anyone get this resolved?
otivbotivb
We finally got the issue resolved by identifying an APEX Class that required us to bring the API level up to at least V.29 (we brought it up to V.40).  Salesforce R&D got involved to help our partner identify the class. You might be able to identify the class by first running "Compile All Classes" under APEX Classes and then reviewing the list of classes - look for anything that does not have the "Is Valid" indicator checked.