You need to sign in to do that
Don't have an account?
Matthew VanderMeer 10
No such column 'NameSpace__Geolocation__c' on entity 'Account'.
I cannot deploy version 3.156 of my managed package. I am able to deploy a lower version (3.155) and then deploy 3.156 without issue. When I deploy the most updated version I get the following error.
1. Dependent class is invalid and needs recompilation:
Class NameSpace.tLP_EmailNotificationList_Functions :
AND DISTANCE(NameSpace__Geolocation__c, GEOLOCATION(:lat
^
ERROR at Row:2:Column:45
No such column 'NameSpace__Geolocation__c' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.
tLP_EmailNotificationList_Trigger: Dependent class is invalid and needs recompilation:
Class NameSpace.tLP_EmailNotificationList_Functions :
AND DISTANCE(NameSpace__Geolocation__c, GEOLOCATION(:lat
However the field 'NameSpace__Geolocation__c' has existed in the managed package since the earliest version (1.4) so I know that the field exists. As well I was able to create this package and subsequent packages and all test cases have passed with sufficient code coverage. I can't understand why installing 3.155 and then 3.156 works without issue but installing 3.156 fails with the above error.
Has anyone else encountered this problem? Did you find a work around? This is causing us some pretty major difficulties.
1. Dependent class is invalid and needs recompilation:
Class NameSpace.tLP_EmailNotificationList_Functions :
AND DISTANCE(NameSpace__Geolocation__c, GEOLOCATION(:lat
^
ERROR at Row:2:Column:45
No such column 'NameSpace__Geolocation__c' on entity 'Account'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.
tLP_EmailNotificationList_Trigger: Dependent class is invalid and needs recompilation:
Class NameSpace.tLP_EmailNotificationList_Functions :
AND DISTANCE(NameSpace__Geolocation__c, GEOLOCATION(:lat
However the field 'NameSpace__Geolocation__c' has existed in the managed package since the earliest version (1.4) so I know that the field exists. As well I was able to create this package and subsequent packages and all test cases have passed with sufficient code coverage. I can't understand why installing 3.155 and then 3.156 works without issue but installing 3.156 fails with the above error.
Has anyone else encountered this problem? Did you find a work around? This is causing us some pretty major difficulties.
All Answers
It took us awhile to find all the pages that referenced this particular class / trigger. We now have our entire package up to version 33 or later and now our package installs correctly. You were a lifesaver!