No such column 'DeveloperName' on entity 'RecordType' after Summer '19 release on sandbox
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
edited May 9 at 15:39
David Reed♦
43.4k82564
asked May 9 at 15:38
N..N..
912421
|
show 1 more comment
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
edited May 9 at 15:39
David Reed♦
43.4k82564
asked May 9 at 15:38
N..N..
912421
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
May 9 at 15:45
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..
May 9 at 16:01
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
May 9 at 16:07
1
@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.
– Jayant Das
May 9 at 16:14
Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.
– N..
May 9 at 16:14
|
show 1 more comment
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
edited May 9 at 15:39
David Reed♦
43.4k82564
asked May 9 at 15:38
N..N..
912421
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
lightning-aura-components record-type summer19
edited May 9 at 15:39
David Reed♦
43.4k82564
asked May 9 at 15:38
N..N..
912421
edited May 9 at 15:39
David Reed♦
43.4k82564
asked May 9 at 15:38
N..N..
912421
edited May 9 at 15:39
David Reed♦
43.4k82564
edited May 9 at 15:39
David Reed♦
43.4k82564
edited May 9 at 15:39
David Reed♦
43.4k82564
43.4k82564
asked May 9 at 15:38
N..N..
912421
asked May 9 at 15:38
N..N..
912421
asked May 9 at 15:38
N..N..
912421
912421
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
May 9 at 15:45
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..
May 9 at 16:01
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
May 9 at 16:07
1
@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.
– Jayant Das
May 9 at 16:14
Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.
– N..
May 9 at 16:14
|
show 1 more comment
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
May 9 at 15:45
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..
May 9 at 16:01
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
May 9 at 16:07
1
@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.
– Jayant Das
May 9 at 16:14
Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.
– N..
May 9 at 16:14
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
May 9 at 15:45
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
May 9 at 15:45
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..
May 9 at 16:01
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..
May 9 at 16:01
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
May 9 at 16:07
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
May 9 at 16:07
1
1
@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.
– Jayant Das
May 9 at 16:14
@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.
– Jayant Das
May 9 at 16:14
Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.
– N..
May 9 at 16:14
Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.
– N..
May 9 at 16:14
|
show 1 more comment
2 Answers
2
active
oldest
votes
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.
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
1
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
1
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
add a comment |
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
answered May 9 at 16:35
sdandamud1sdandamud1
4027
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..
May 9 at 16:58
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
1
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
1
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
add a comment |
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.
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
1
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
1
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
add a comment |
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.
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
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.
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
answered May 9 at 16:23
Ashish SharmaAshish Sharma
730316
730316
1
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
1
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
add a comment |
1
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
1
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
1
1
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
To all those having similar issue, 'Compile all classes' works. But I had to do it more than once. I did it yesterday, all was good. Today I login to continue working on my Lightning Component and I got same issue. So I had to 'Compile all classes' again. Until Salesforce applies a patch, we may need to compile all classes a few times.
– N..
May 10 at 10:25
1
1
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
This release is still in preview. So I am pretty sure that before GA, Salesforce will resolve this or they will not release the update which is causing this.
– Ashish Sharma
May 10 at 11:16
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
I agree on this point, Ashish. Hoping for a fix soon though.
– N..
May 10 at 11:43
add a comment |
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
answered May 9 at 16:35
sdandamud1sdandamud1
4027
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..
May 9 at 16:58
add a comment |
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
answered May 9 at 16:35
sdandamud1sdandamud1
4027
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..
May 9 at 16:58
add a comment |
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
answered May 9 at 16:35
sdandamud1sdandamud1
4027
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
answered May 9 at 16:35
sdandamud1sdandamud1
4027
answered May 9 at 16:35
sdandamud1sdandamud1
4027
answered May 9 at 16:35
sdandamud1sdandamud1
4027
answered May 9 at 16:35
sdandamud1sdandamud1
4027
4027
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..
May 9 at 16:58
add a comment |
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..
May 9 at 16:58
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..
May 9 at 16:58
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..
May 9 at 16:58
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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
May 9 at 15:45
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..
May 9 at 16:01
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
May 9 at 16:07
1
@AshishSharma You should add your comments as an answer as that seemed to be the resolution here.
– Jayant Das
May 9 at 16:14
Ok @AshishSharma. Thank you so much for your help. I shall keep that in mind.
– N..
May 9 at 16:14