WorkOrder. Deploy Trigger. Entity is not API accessible.

Question

WorkOrder. Deploy Trigger. Entity is not API accessible.

HBIND2020 opened this issue 8 years ago · 6 comments

HBIND2020 commented 8 years ago

Hallo All,

I am trying to roll up from WorkOrder (Standard Object) to a Custom Object and getting Entity is not api accessible error, entity name: WorkOrder. Seems the object is available in API version 36.0 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_workorder.htm. I am on version 2.8 - so should be using API 37.0. What else do I need to look at?

Thanks!!

afawcett commented 7 years ago

v2.9

Answer 1 · 2017-03-26T16:53:28.000Z

Ah i see the problem, the generated code is still using API 32! This is a bug. https://github.com/afawcett/declarative-lookup-rollup-summaries/blob/master/rolluptool/src/classes/RollupController.cls#L195. Should be easy to fix and explains a few other folks posting stuff like this!

Answer 2 · 2017-03-27T12:35:10.000Z

I generated the Apex Trigger and Test Class using API Version 37.0. That worked. Thank you!

Answer 3 · 2017-05-22T19:28:52.000Z

@HBIND2020 How did you generate the Trigger & Test Class with a different API version? Are you running unmanaged version?

Answer 4 · 2017-05-22T20:55:52.000Z

No, I use the Managed Package!
Steps to generate the code:

Click on Manage Child Trigger.
A new page will open with the code for the Apex Trigger and Test Class needed.
Use a tool like Developer Console to generate it in the API version needed in a sandbox.
Move to production using a change set.

Answer 5 · 2017-05-22T21:05:38.000Z

Yes, that's what I did too; was wondering if there was an easier way. This issue should not be closed though, because the bug is absolutely still there and needs to be fixed.