trigger on Question object gives below error during the deployment

Question

I have been getting below error when trying to deploy new changes from sandbox to production.

chatter_answers_question_escalation_to_case_trigger: trigger body is invalid and failed recompilation: Entity is not org-accessible Stack Trace: null

This is a trigger on Question (chatter Question) object which I can't find it after summer 16 release. Last successful deployment was on 06/09 and only change we did since yesterday was recompiled all classes and ran All tests.

Any help is greatly appreciated.

Answer 1

I'm going to surmise that Chatter Questions is not enabled in your PROD org. Per Help doc:

To enable Chatter Questions in your organization, add the Question action to the global publisher layout. If your organization was created after Summer ‘14, the Question action is automatically added, but we recommend dragging it to the far left to increase its visibility. If you’re using a customized publisher layout in groups or on records, make sure that the Question action is added to those layouts as well.

Answer 2

Do do have Chatter Answers enabled for the production. This can be cause of the issue! You should log a case with support to get it enabled.

Answer 3

I had the same issue, Since we do not use chatter answers I deleted the chatter_answers_question_escalation_to_case_trigger from production using workbench to deploy the following meta data and checking the Ignore Warnings checkbox.

package.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <version>37.0</version>
</Package>

destructiveChanges.xml:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
<types>
    <members>chatter_answers_question_escalation_to_case_trigger</members>
    <name>ApexTrigger</name>
</types>
<version>37.0</version>
</Package>

Hope this helps you deploy change sets in the mean time.

Answer 4

here is an additional thing that may help you.

I was using a brand new Salesforce Production Instance build on Spring 17.

When I started the deployment into Production instance, I bumped into the above error.

ChatterAnswersEscalationTriggerTest line 17, column 13: No such column 'CommunityId' on entity 'Case'. 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. Stack Trace: null

chatter_answers_question_escalation_to_case_trigger: trigger body is invalid and failed recompilation: Entity is not org-accessible Stack Trace: null

As I had done during my Sandbox deployment, I uploaded the package to delete the Trigger and Apex Class that caused these 2 issues.

With very little trouble I deployed it into Sandbox as it did not demand me the code coverage.

When I did the same in Prod, as these where Apex Deployment, it required me to have a code Coverage of 75% instead of 0%. In order to get around the problem, not sure if that is the best option, I wrote a dummy Apex Class and a supporting test class, had few method built up with around 300 lines of code that was covered on running the test class.

Once tested in Sandbox, I deployed the same in Production and bingo it worked like a charm.

here is the update package.xml where InitialCodeCoverage and InitialCodeCoverage_UT are the dummy apex classes I wrote for code coverage.

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>ChatterAnswersEscalationTriggerTest</members>
        <members>InitialCodeCoverage</members>
        <members>InitialCodeCoverage_UT</members>
        <name>ApexClass</name>
    </types>
    <types>           <members>chatter_answers_question_escalation_to_case_trigger</members>
        <name>ApexTrigger</name>
    </types>
    <version>37.0</version>
</Package>

When I deployed my actual package, I marked these files as deleted thus making sure it does not interfere in my future code coverage.

Answer 5

I believe the reason you're having this problem is that the Question Object changed with the Summer 16 release. The API 37 version of Question is not the same as the API 36 version of Question object. Your trigger is trying to reference one API's version, but finding a different version which it isn't recognizing.

On the surface it would appear there wouldn't be a difference, but I happened to have the SP16 Object Reference in PDF format and compared it to the SU16 Object Reference for Question in the latest docs. I found an unusual reference in the BestReplySelectedById field in SP16 version compared to SU16 which is as follows:

Description

The ID of the User who selected the best answer to the question. This field is available in API version 24.0 and later. In API version 24.0 through version 29.0, you must update this field using the UI. In API version 36.0 and later, you can update this field using the API.

What's interesting is that in the SU17 version, for the same field, it has this:

Description

The ID of the User who selected the best answer to the question. This field is available in API version 24.0 and later. In API version 24.0 through version 29.0, you must update this field using the UI. In API version 37.0 and later, you can update this field using the API.

What the above says to me, is that Salesforce changed the BestReplySelectedById field both in SP16 and SU16! The API version of the Question object is likely creating the issue you're having. If I understand what you've described correctly, what you need to do to solve your problem is deploy the API 37 Question Object to your org along with your API 37 trigger for you to be able to deploy it and have it work with your production org. It's likely they're not at the same API version.

You may also want to look at the SU16 Release Notes regarding the numerous changes that came up related to Chatter Questions.

Answer 6

For the chatter_answers_question_escalation_to_case_trigger, i'm not able to delete it via workbench also. I'm lacking coverage when I'm not running all the local test classes. When running all, The chatter trigger test class is generating error. I don't believe salesforce is letting a big BUG like this.