Unable access to opportunity object fields in apex classes and trigger?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












2















enter image description here Unable to access opportunity object fields in apex classes and in triggers also .even in the standard way of creating apex classes. getting an error as variable doesn't Exist, even field is available.
please help me out on this










share|improve this question






















  • In the future, you should upload your code as text instead of a screenshot. It's easier to copy into an answer & easier to read.

    – battery.cord
    Feb 6 at 14:55











  • @battery.cord yaa sure

    – Akhil Thanneru
    Feb 7 at 6:59















2















enter image description here Unable to access opportunity object fields in apex classes and in triggers also .even in the standard way of creating apex classes. getting an error as variable doesn't Exist, even field is available.
please help me out on this










share|improve this question






















  • In the future, you should upload your code as text instead of a screenshot. It's easier to copy into an answer & easier to read.

    – battery.cord
    Feb 6 at 14:55











  • @battery.cord yaa sure

    – Akhil Thanneru
    Feb 7 at 6:59













2












2








2








enter image description here Unable to access opportunity object fields in apex classes and in triggers also .even in the standard way of creating apex classes. getting an error as variable doesn't Exist, even field is available.
please help me out on this










share|improve this question














enter image description here Unable to access opportunity object fields in apex classes and in triggers also .even in the standard way of creating apex classes. getting an error as variable doesn't Exist, even field is available.
please help me out on this







apex






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 6 at 6:47









Akhil ThanneruAkhil Thanneru

133




133












  • In the future, you should upload your code as text instead of a screenshot. It's easier to copy into an answer & easier to read.

    – battery.cord
    Feb 6 at 14:55











  • @battery.cord yaa sure

    – Akhil Thanneru
    Feb 7 at 6:59

















  • In the future, you should upload your code as text instead of a screenshot. It's easier to copy into an answer & easier to read.

    – battery.cord
    Feb 6 at 14:55











  • @battery.cord yaa sure

    – Akhil Thanneru
    Feb 7 at 6:59
















In the future, you should upload your code as text instead of a screenshot. It's easier to copy into an answer & easier to read.

– battery.cord
Feb 6 at 14:55





In the future, you should upload your code as text instead of a screenshot. It's easier to copy into an answer & easier to read.

– battery.cord
Feb 6 at 14:55













@battery.cord yaa sure

– Akhil Thanneru
Feb 7 at 6:59





@battery.cord yaa sure

– Akhil Thanneru
Feb 7 at 6:59










1 Answer
1






active

oldest

votes


















7














This happens when your organization has a class named as Opportunity.



Check in your list of classes which is named as Opportunity and rename it to something else.



Compiler searches for Amount property in your custom made Opportunity class which if doesn't exist, then it gives an compilation error.



Note : You should never create classes with the names which are already being used by the platform.






share|improve this answer























  • even after renaming the class unable to access fields

    – Akhil Thanneru
    Feb 6 at 10:05






  • 1





    Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

    – Vijay Ganji
    Feb 6 at 10:36










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f249275%2funable-access-to-opportunity-object-fields-in-apex-classes-and-trigger%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









7














This happens when your organization has a class named as Opportunity.



Check in your list of classes which is named as Opportunity and rename it to something else.



Compiler searches for Amount property in your custom made Opportunity class which if doesn't exist, then it gives an compilation error.



Note : You should never create classes with the names which are already being used by the platform.






share|improve this answer























  • even after renaming the class unable to access fields

    – Akhil Thanneru
    Feb 6 at 10:05






  • 1





    Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

    – Vijay Ganji
    Feb 6 at 10:36















7














This happens when your organization has a class named as Opportunity.



Check in your list of classes which is named as Opportunity and rename it to something else.



Compiler searches for Amount property in your custom made Opportunity class which if doesn't exist, then it gives an compilation error.



Note : You should never create classes with the names which are already being used by the platform.






share|improve this answer























  • even after renaming the class unable to access fields

    – Akhil Thanneru
    Feb 6 at 10:05






  • 1





    Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

    – Vijay Ganji
    Feb 6 at 10:36













7












7








7







This happens when your organization has a class named as Opportunity.



Check in your list of classes which is named as Opportunity and rename it to something else.



Compiler searches for Amount property in your custom made Opportunity class which if doesn't exist, then it gives an compilation error.



Note : You should never create classes with the names which are already being used by the platform.






share|improve this answer













This happens when your organization has a class named as Opportunity.



Check in your list of classes which is named as Opportunity and rename it to something else.



Compiler searches for Amount property in your custom made Opportunity class which if doesn't exist, then it gives an compilation error.



Note : You should never create classes with the names which are already being used by the platform.







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 6 at 7:04









Vijay GanjiVijay Ganji

844211




844211












  • even after renaming the class unable to access fields

    – Akhil Thanneru
    Feb 6 at 10:05






  • 1





    Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

    – Vijay Ganji
    Feb 6 at 10:36

















  • even after renaming the class unable to access fields

    – Akhil Thanneru
    Feb 6 at 10:05






  • 1





    Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

    – Vijay Ganji
    Feb 6 at 10:36
















even after renaming the class unable to access fields

– Akhil Thanneru
Feb 6 at 10:05





even after renaming the class unable to access fields

– Akhil Thanneru
Feb 6 at 10:05




1




1





Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

– Vijay Ganji
Feb 6 at 10:36





Compile all your classes post renaming and then try saving your trigger changes. You can compile all classes by navigating from Setup > Develop > Apex Classes > Click on Compile all classes

– Vijay Ganji
Feb 6 at 10:36

















draft saved

draft discarded
















































Thanks for contributing an answer to Salesforce Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f249275%2funable-access-to-opportunity-object-fields-in-apex-classes-and-trigger%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)