Dynamic Return Type
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Is it possible to create a method that will return any sObject type?
Why?
I want to create a method that combines DML operations, but the initial method that is called should be able to return any sObject type.
apex
add a comment |
Is it possible to create a method that will return any sObject type?
Why?
I want to create a method that combines DML operations, but the initial method that is called should be able to return any sObject type.
apex
add a comment |
Is it possible to create a method that will return any sObject type?
Why?
I want to create a method that combines DML operations, but the initial method that is called should be able to return any sObject type.
apex
Is it possible to create a method that will return any sObject type?
Why?
I want to create a method that combines DML operations, but the initial method that is called should be able to return any sObject type.
apex
apex
asked 7 hours ago
Matthew MetrosMatthew Metros
311
311
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can always create a method to return a SObject. Something as below:
public SObject mySObject() {
if(condition) {
return new Account();
} else {
return new Contact();
}
}
It will though depend on how you want to utilize it from your calling context. You can always get the SObjectType in your calling context and take actions accordingly. E.g.,
SObject s = mySobject();
system.debug(s.getSObjectType());
// execute other code based on type
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
You can also useinstanceof(e.g.if(s instanceof Account)) or a switch statement
– IllusiveBrian
3 hours ago
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%2f259947%2fdynamic-return-type%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
You can always create a method to return a SObject. Something as below:
public SObject mySObject() {
if(condition) {
return new Account();
} else {
return new Contact();
}
}
It will though depend on how you want to utilize it from your calling context. You can always get the SObjectType in your calling context and take actions accordingly. E.g.,
SObject s = mySobject();
system.debug(s.getSObjectType());
// execute other code based on type
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
You can also useinstanceof(e.g.if(s instanceof Account)) or a switch statement
– IllusiveBrian
3 hours ago
add a comment |
You can always create a method to return a SObject. Something as below:
public SObject mySObject() {
if(condition) {
return new Account();
} else {
return new Contact();
}
}
It will though depend on how you want to utilize it from your calling context. You can always get the SObjectType in your calling context and take actions accordingly. E.g.,
SObject s = mySobject();
system.debug(s.getSObjectType());
// execute other code based on type
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
You can also useinstanceof(e.g.if(s instanceof Account)) or a switch statement
– IllusiveBrian
3 hours ago
add a comment |
You can always create a method to return a SObject. Something as below:
public SObject mySObject() {
if(condition) {
return new Account();
} else {
return new Contact();
}
}
It will though depend on how you want to utilize it from your calling context. You can always get the SObjectType in your calling context and take actions accordingly. E.g.,
SObject s = mySobject();
system.debug(s.getSObjectType());
// execute other code based on type
You can always create a method to return a SObject. Something as below:
public SObject mySObject() {
if(condition) {
return new Account();
} else {
return new Contact();
}
}
It will though depend on how you want to utilize it from your calling context. You can always get the SObjectType in your calling context and take actions accordingly. E.g.,
SObject s = mySobject();
system.debug(s.getSObjectType());
// execute other code based on type
edited 6 hours ago
answered 7 hours ago
Jayant DasJayant Das
19.2k21331
19.2k21331
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
You can also useinstanceof(e.g.if(s instanceof Account)) or a switch statement
– IllusiveBrian
3 hours ago
add a comment |
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
You can also useinstanceof(e.g.if(s instanceof Account)) or a switch statement
– IllusiveBrian
3 hours ago
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
even better is to return a List<SObject> so caller can work with collection idioms
– cropredy
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
@cropredy Agreed. This was more of a direct answer to the question itself, definitely always scope of improvements/refinement based on actual requirements.
– Jayant Das
4 hours ago
You can also use
instanceof (e.g. if(s instanceof Account)) or a switch statement– IllusiveBrian
3 hours ago
You can also use
instanceof (e.g. if(s instanceof Account)) or a switch statement– IllusiveBrian
3 hours ago
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%2f259947%2fdynamic-return-type%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