List view button without standard controller
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
Is it possible to create a list view button without a standard controller?
My requirement is, I want to create a List view button for any object. In the current scenario, I have to write the same logic for multiple objects.
for example :
<apex:page showHeader="false" sidebar="false" standardController="Account" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Contact" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Custome_Object" extensions="BulkSMSController" recordSetVar="Member">
Is it possible to write dynamic standard controller?
visualforce visualforce-component dynamic-visualforce dynamic-apex dynamic-vf-component
add a comment |
Is it possible to create a list view button without a standard controller?
My requirement is, I want to create a List view button for any object. In the current scenario, I have to write the same logic for multiple objects.
for example :
<apex:page showHeader="false" sidebar="false" standardController="Account" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Contact" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Custome_Object" extensions="BulkSMSController" recordSetVar="Member">
Is it possible to write dynamic standard controller?
visualforce visualforce-component dynamic-visualforce dynamic-apex dynamic-vf-component
add a comment |
Is it possible to create a list view button without a standard controller?
My requirement is, I want to create a List view button for any object. In the current scenario, I have to write the same logic for multiple objects.
for example :
<apex:page showHeader="false" sidebar="false" standardController="Account" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Contact" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Custome_Object" extensions="BulkSMSController" recordSetVar="Member">
Is it possible to write dynamic standard controller?
visualforce visualforce-component dynamic-visualforce dynamic-apex dynamic-vf-component
Is it possible to create a list view button without a standard controller?
My requirement is, I want to create a List view button for any object. In the current scenario, I have to write the same logic for multiple objects.
for example :
<apex:page showHeader="false" sidebar="false" standardController="Account" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Contact" extensions="BulkSMSController" recordSetVar="Member">
<apex:page showHeader="false" sidebar="false" standardController="Custome_Object" extensions="BulkSMSController" recordSetVar="Member">
Is it possible to write dynamic standard controller?
visualforce visualforce-component dynamic-visualforce dynamic-apex dynamic-vf-component
visualforce visualforce-component dynamic-visualforce dynamic-apex dynamic-vf-component
edited 1 hour ago
Robs
2,609743
2,609743
asked 1 hour ago
GmDeepakChounan21GmDeepakChounan21
448
448
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No. The best you can do is move the core markup you want to not duplicate into a Visualforce Component
instead. You need one top level Visualforce Page
for each object you wish to support, end of story.
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%2f260429%2flist-view-button-without-standard-controller%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
No. The best you can do is move the core markup you want to not duplicate into a Visualforce Component
instead. You need one top level Visualforce Page
for each object you wish to support, end of story.
add a comment |
No. The best you can do is move the core markup you want to not duplicate into a Visualforce Component
instead. You need one top level Visualforce Page
for each object you wish to support, end of story.
add a comment |
No. The best you can do is move the core markup you want to not duplicate into a Visualforce Component
instead. You need one top level Visualforce Page
for each object you wish to support, end of story.
No. The best you can do is move the core markup you want to not duplicate into a Visualforce Component
instead. You need one top level Visualforce Page
for each object you wish to support, end of story.
answered 54 mins ago
Adrian Larson♦Adrian Larson
111k19122260
111k19122260
add a comment |
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%2f260429%2flist-view-button-without-standard-controller%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