No such column 'DeveloperName' on entity 'RecordType' after Summer '19 release on sandboxFlow error - The field “Name” isn’t valid for the “Contact” object after Summer 19 previewUnable to load jQuery in Salesforce Lightning Application after Salesforce Locker Service enable in Summer '16 ReleaseInvalid field RecordTypeId for SObject CaseCustom Lightning Components Failing with the new Summer '17 Release?How do you access the user's choice for RecordType when using a lightning component to override the New button on a custom object?Lightning Component/Inner Class Bug after Spring 18 sandbox updateProblem with sending Date as string from Aura to Apex. (after Summer 18 release on sandbox)Uncaught Assertion Failed - label attribute requiredUncaught TypeError Issue with the Lightning datepicker Introduced in Summer '18How to get object metadata like recordtypes entirely clientside in a Lightning Component?Unable to save Existing Lightning Components after Summer19 release sandboxes

Can the president of the United States be guilty of insider trading?

Can a surprised creature fall prone voluntarily on their turn?

How to handle DM constantly stealing everything from sleeping characters?

Why use steam instead of just hot air?

Why are low spin tetrahedral complexes so rare?

Remove color cast in darktable?

Succinct and gender-neutral Russian word for "writer"

A Cunning Riley Riddle

What food production methods would allow a metropolis like New York to become self sufficient

Equivalent for "Make the jacket to the button"

How to get the IP of a user who executed a command?

Has there been evidence of any other gods?

cropping a message using array splits

Why is it wrong to *implement* myself a known, published, widely believed to be secure crypto algorithm?

What's the "magic similar to the Knock spell" referenced in the Dungeon of the Mad Mage adventure?

Exception propagation: When to catch exceptions?

Why does increasing the sampling rate make implementing an anti-aliasing filter easier?

Pre-1993 comic in which Wolverine's claws were turned to rubber?

Why is the Sun made of light elements only?

Is there an application which does HTTP PUT?

Why did Captain America age?

How do I compare the result of "1d20+x, with advantage" to "1d20+y, without advantage", assuming x < y?

Passport stamps art, can it be done?

Has magnetic core memory been used beyond the Moon?



No such column 'DeveloperName' on entity 'RecordType' after Summer '19 release on sandbox


Flow error - The field “Name” isn’t valid for the “Contact” object after Summer 19 previewUnable to load jQuery in Salesforce Lightning Application after Salesforce Locker Service enable in Summer '16 ReleaseInvalid field RecordTypeId for SObject CaseCustom Lightning Components Failing with the new Summer '17 Release?How do you access the user's choice for RecordType when using a lightning component to override the New button on a custom object?Lightning Component/Inner Class Bug after Spring 18 sandbox updateProblem with sending Date as string from Aura to Apex. (after Summer 18 release on sandbox)Uncaught Assertion Failed - label attribute requiredUncaught TypeError Issue with the Lightning datepicker Introduced in Summer '18How to get object metadata like recordtypes entirely clientside in a Lightning Component?Unable to save Existing Lightning Components after Summer19 release sandboxes






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








6















I am getting the error




No such column 'DeveloperName' on entity 'RecordType'. 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.: Source




when saving a Lightning component on my sandbox after Summer '19 release.



The Lightning component is using an Apex class where the below code is causing the error :



Set<String> objAPINames = new Set<String>'Account', 'Opportunity';
Map<String,Id> mapValues = new Map<String,Id>();
for(RecordType rt : [select SobjectType, DeveloperName, Id
from RecordType
where SobjectType IN :objAPINames
order by SobjectType ASC ])
mapValues.put(rt.DeveloperName, rt.Id);



This code works fine in Developer Console, Apex Classes, Triggers.
It is only causing error when I am saving Lightning Component calling the class.



Anyone got this issue after the new release?










share|improve this question



















  • 2





    Did you try recompiling all the classes in your org. Go to apex classes under setup and use compile all classes link. We faced something similar and got it fixed by recompiling all the classes

    – Ashish Sharma
    9 hours ago











  • Thank you so much @AshishSharma. It worked. I need to deploy those Lightning Components and classes to another Summer '19 sandbox and a Spring '19 production environment. The code does not exist in those org. yet. Do you think there will be similar issue while deploying?

    – N..
    9 hours ago






  • 1





    I am not sure but It should not be an issue as this will be new metadata moving to target org. In case if it causes any issue, you can always deploy it in parts. First moving the classes, compile the classes/run test classes and then deploy lightning component.

    – Ashish Sharma
    9 hours ago






  • 1





    @AshishSharma You should add your comments as an answer as that seemed to be the resolution here.

    – Jayant Das
    9 hours ago











  • Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.

    – N..
    9 hours ago

















6















I am getting the error




No such column 'DeveloperName' on entity 'RecordType'. 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.: Source




when saving a Lightning component on my sandbox after Summer '19 release.



The Lightning component is using an Apex class where the below code is causing the error :



Set<String> objAPINames = new Set<String>'Account', 'Opportunity';
Map<String,Id> mapValues = new Map<String,Id>();
for(RecordType rt : [select SobjectType, DeveloperName, Id
from RecordType
where SobjectType IN :objAPINames
order by SobjectType ASC ])
mapValues.put(rt.DeveloperName, rt.Id);



This code works fine in Developer Console, Apex Classes, Triggers.
It is only causing error when I am saving Lightning Component calling the class.



Anyone got this issue after the new release?










share|improve this question



















  • 2





    Did you try recompiling all the classes in your org. Go to apex classes under setup and use compile all classes link. We faced something similar and got it fixed by recompiling all the classes

    – Ashish Sharma
    9 hours ago











  • Thank you so much @AshishSharma. It worked. I need to deploy those Lightning Components and classes to another Summer '19 sandbox and a Spring '19 production environment. The code does not exist in those org. yet. Do you think there will be similar issue while deploying?

    – N..
    9 hours ago






  • 1





    I am not sure but It should not be an issue as this will be new metadata moving to target org. In case if it causes any issue, you can always deploy it in parts. First moving the classes, compile the classes/run test classes and then deploy lightning component.

    – Ashish Sharma
    9 hours ago






  • 1





    @AshishSharma You should add your comments as an answer as that seemed to be the resolution here.

    – Jayant Das
    9 hours ago











  • Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.

    – N..
    9 hours ago













6












6








6








I am getting the error




No such column 'DeveloperName' on entity 'RecordType'. 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.: Source




when saving a Lightning component on my sandbox after Summer '19 release.



The Lightning component is using an Apex class where the below code is causing the error :



Set<String> objAPINames = new Set<String>'Account', 'Opportunity';
Map<String,Id> mapValues = new Map<String,Id>();
for(RecordType rt : [select SobjectType, DeveloperName, Id
from RecordType
where SobjectType IN :objAPINames
order by SobjectType ASC ])
mapValues.put(rt.DeveloperName, rt.Id);



This code works fine in Developer Console, Apex Classes, Triggers.
It is only causing error when I am saving Lightning Component calling the class.



Anyone got this issue after the new release?










share|improve this question
















I am getting the error




No such column 'DeveloperName' on entity 'RecordType'. 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.: Source




when saving a Lightning component on my sandbox after Summer '19 release.



The Lightning component is using an Apex class where the below code is causing the error :



Set<String> objAPINames = new Set<String>'Account', 'Opportunity';
Map<String,Id> mapValues = new Map<String,Id>();
for(RecordType rt : [select SobjectType, DeveloperName, Id
from RecordType
where SobjectType IN :objAPINames
order by SobjectType ASC ])
mapValues.put(rt.DeveloperName, rt.Id);



This code works fine in Developer Console, Apex Classes, Triggers.
It is only causing error when I am saving Lightning Component calling the class.



Anyone got this issue after the new release?







lightning-aura-components record-type summer19






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 9 hours ago









David Reed

41.7k82463




41.7k82463










asked 9 hours ago









N..N..

909421




909421







  • 2





    Did you try recompiling all the classes in your org. Go to apex classes under setup and use compile all classes link. We faced something similar and got it fixed by recompiling all the classes

    – Ashish Sharma
    9 hours ago











  • Thank you so much @AshishSharma. It worked. I need to deploy those Lightning Components and classes to another Summer '19 sandbox and a Spring '19 production environment. The code does not exist in those org. yet. Do you think there will be similar issue while deploying?

    – N..
    9 hours ago






  • 1





    I am not sure but It should not be an issue as this will be new metadata moving to target org. In case if it causes any issue, you can always deploy it in parts. First moving the classes, compile the classes/run test classes and then deploy lightning component.

    – Ashish Sharma
    9 hours ago






  • 1





    @AshishSharma You should add your comments as an answer as that seemed to be the resolution here.

    – Jayant Das
    9 hours ago











  • Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.

    – N..
    9 hours ago












  • 2





    Did you try recompiling all the classes in your org. Go to apex classes under setup and use compile all classes link. We faced something similar and got it fixed by recompiling all the classes

    – Ashish Sharma
    9 hours ago











  • Thank you so much @AshishSharma. It worked. I need to deploy those Lightning Components and classes to another Summer '19 sandbox and a Spring '19 production environment. The code does not exist in those org. yet. Do you think there will be similar issue while deploying?

    – N..
    9 hours ago






  • 1





    I am not sure but It should not be an issue as this will be new metadata moving to target org. In case if it causes any issue, you can always deploy it in parts. First moving the classes, compile the classes/run test classes and then deploy lightning component.

    – Ashish Sharma
    9 hours ago






  • 1





    @AshishSharma You should add your comments as an answer as that seemed to be the resolution here.

    – Jayant Das
    9 hours ago











  • Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.

    – N..
    9 hours ago







2




2





Did you try recompiling all the classes in your org. Go to apex classes under setup and use compile all classes link. We faced something similar and got it fixed by recompiling all the classes

– Ashish Sharma
9 hours ago





Did you try recompiling all the classes in your org. Go to apex classes under setup and use compile all classes link. We faced something similar and got it fixed by recompiling all the classes

– Ashish Sharma
9 hours ago













Thank you so much @AshishSharma. It worked. I need to deploy those Lightning Components and classes to another Summer '19 sandbox and a Spring '19 production environment. The code does not exist in those org. yet. Do you think there will be similar issue while deploying?

– N..
9 hours ago





Thank you so much @AshishSharma. It worked. I need to deploy those Lightning Components and classes to another Summer '19 sandbox and a Spring '19 production environment. The code does not exist in those org. yet. Do you think there will be similar issue while deploying?

– N..
9 hours ago




1




1





I am not sure but It should not be an issue as this will be new metadata moving to target org. In case if it causes any issue, you can always deploy it in parts. First moving the classes, compile the classes/run test classes and then deploy lightning component.

– Ashish Sharma
9 hours ago





I am not sure but It should not be an issue as this will be new metadata moving to target org. In case if it causes any issue, you can always deploy it in parts. First moving the classes, compile the classes/run test classes and then deploy lightning component.

– Ashish Sharma
9 hours ago




1




1





@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.

– Jayant Das
9 hours ago





@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.

– Jayant Das
9 hours ago













Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.

– N..
9 hours ago





Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.

– N..
9 hours ago










2 Answers
2






active

oldest

votes


















6














Please recompile all classes in org by using compile all classes link on apex classes page under setup or you can do runAllTest in org which will recompile the covered classes. This will fix the issue. We faced a similar issue after Summer 19 release and got it fixed by recompiling all the classes.






share|improve this answer






























    2














    Check this Know Issue with workaround:
    salseforce known issue



    ​​​​​​Workaround
    Use Metadata Api or VS Code and SFDX to deploy changes to your lightning components






    share|improve this answer























    • Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

      – N..
      8 hours ago











    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%2f261799%2fno-such-column-developername-on-entity-recordtype-after-summer-19-release-o%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    6














    Please recompile all classes in org by using compile all classes link on apex classes page under setup or you can do runAllTest in org which will recompile the covered classes. This will fix the issue. We faced a similar issue after Summer 19 release and got it fixed by recompiling all the classes.






    share|improve this answer



























      6














      Please recompile all classes in org by using compile all classes link on apex classes page under setup or you can do runAllTest in org which will recompile the covered classes. This will fix the issue. We faced a similar issue after Summer 19 release and got it fixed by recompiling all the classes.






      share|improve this answer

























        6












        6








        6







        Please recompile all classes in org by using compile all classes link on apex classes page under setup or you can do runAllTest in org which will recompile the covered classes. This will fix the issue. We faced a similar issue after Summer 19 release and got it fixed by recompiling all the classes.






        share|improve this answer













        Please recompile all classes in org by using compile all classes link on apex classes page under setup or you can do runAllTest in org which will recompile the covered classes. This will fix the issue. We faced a similar issue after Summer 19 release and got it fixed by recompiling all the classes.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 8 hours ago









        Ashish SharmaAshish Sharma

        568215




        568215























            2














            Check this Know Issue with workaround:
            salseforce known issue



            ​​​​​​Workaround
            Use Metadata Api or VS Code and SFDX to deploy changes to your lightning components






            share|improve this answer























            • Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

              – N..
              8 hours ago















            2














            Check this Know Issue with workaround:
            salseforce known issue



            ​​​​​​Workaround
            Use Metadata Api or VS Code and SFDX to deploy changes to your lightning components






            share|improve this answer























            • Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

              – N..
              8 hours ago













            2












            2








            2







            Check this Know Issue with workaround:
            salseforce known issue



            ​​​​​​Workaround
            Use Metadata Api or VS Code and SFDX to deploy changes to your lightning components






            share|improve this answer













            Check this Know Issue with workaround:
            salseforce known issue



            ​​​​​​Workaround
            Use Metadata Api or VS Code and SFDX to deploy changes to your lightning components







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 8 hours ago









            sdandamud1sdandamud1

            666




            666












            • Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

              – N..
              8 hours ago

















            • Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

              – N..
              8 hours ago
















            Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

            – N..
            8 hours ago





            Thanks. I managed to solve the issue by recompiling all Apex Classes as suggested by Ashish. The link to the known issue is useful though. Thank you very much.

            – N..
            8 hours ago

















            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%2f261799%2fno-such-column-developername-on-entity-recordtype-after-summer-19-release-o%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

            Log på Navigationsmenu

            Wonderful Copenhagen (sang) Eksterne henvisninger | NavigationsmenurSide på frankloesser.comWonderful Copenhagen

            Detroit Tigers Spis treści Historia | Skład zespołu | Sukcesy | Członkowie Baseball Hall of Fame | Zastrzeżone numery | Przypisy | Menu nawigacyjneEncyclopedia of Detroit - Detroit TigersTigers Stadium, Detroit, MITigers Timeline 1900sDetroit Tigers Team History & EncyclopediaTigers Timeline 1910s1935 World Series1945 World Series1945 World Series1984 World SeriesComerica Park, Detroit, MI2006 World Series2012 World SeriesDetroit Tigers 40-Man RosterDetroit Tigers Coaching StaffTigers Hall of FamersTigers Retired Numberse