How do I produce a “New” record button to look like a standard “New” button?
Basically I want to create an input area for a new record. I'm trying to get it styled like the standard "New" Button. I have tried doing it via Visualforce but it looks like a completely separate entity.
Before I continue I just want clarification on the best method to use?
Should I stick with Visualforce or figure out how to create Lightning Components?
I find Visualforce much easier to produce and get working but it's nowhere as pretty as lightning components.
The data aspect of Lightning Components I find hard to deal with (all the back end wiring/coding).
Do I have to use the Lightning Data Service with Components or can I use a standard controller like in VF?
This is the standard "New" Layout.
This Is The Visualforce Layout I Created.
This Is The Lightning Component I Made.
Summary Of Questions:-
- Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
- Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
- Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
visualforce lightning-aura-components lightning lightning-design-system modal
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
add a comment |
Basically I want to create an input area for a new record. I'm trying to get it styled like the standard "New" Button. I have tried doing it via Visualforce but it looks like a completely separate entity.
Before I continue I just want clarification on the best method to use?
Should I stick with Visualforce or figure out how to create Lightning Components?
I find Visualforce much easier to produce and get working but it's nowhere as pretty as lightning components.
The data aspect of Lightning Components I find hard to deal with (all the back end wiring/coding).
Do I have to use the Lightning Data Service with Components or can I use a standard controller like in VF?
This is the standard "New" Layout.
This Is The Visualforce Layout I Created.
This Is The Lightning Component I Made.
Summary Of Questions:-
- Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
- Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
- Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
visualforce lightning-aura-components lightning lightning-design-system modal
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
add a comment |
Basically I want to create an input area for a new record. I'm trying to get it styled like the standard "New" Button. I have tried doing it via Visualforce but it looks like a completely separate entity.
Before I continue I just want clarification on the best method to use?
Should I stick with Visualforce or figure out how to create Lightning Components?
I find Visualforce much easier to produce and get working but it's nowhere as pretty as lightning components.
The data aspect of Lightning Components I find hard to deal with (all the back end wiring/coding).
Do I have to use the Lightning Data Service with Components or can I use a standard controller like in VF?
This is the standard "New" Layout.
This Is The Visualforce Layout I Created.
This Is The Lightning Component I Made.
Summary Of Questions:-
- Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
- Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
- Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
visualforce lightning-aura-components lightning lightning-design-system modal
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
Basically I want to create an input area for a new record. I'm trying to get it styled like the standard "New" Button. I have tried doing it via Visualforce but it looks like a completely separate entity.
Before I continue I just want clarification on the best method to use?
Should I stick with Visualforce or figure out how to create Lightning Components?
I find Visualforce much easier to produce and get working but it's nowhere as pretty as lightning components.
The data aspect of Lightning Components I find hard to deal with (all the back end wiring/coding).
Do I have to use the Lightning Data Service with Components or can I use a standard controller like in VF?
This is the standard "New" Layout.
This Is The Visualforce Layout I Created.
This Is The Lightning Component I Made.
Summary Of Questions:-
- Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
- Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
- Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
visualforce lightning-aura-components lightning lightning-design-system modal
visualforce lightning-aura-components lightning lightning-design-system modal
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
edited Dec 11 '18 at 13:29
Adrian Larson♦
105k19112235
105k19112235
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
asked Dec 11 '18 at 13:25
Daniel Bleasdale
266
266
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
Answer: Lightning is the way forward, Salesforce is pitching it with Blood Sweat and tears to make everyone adopt it. Building in lightning would be like futureproofing your application. The key difference between VF and lightning is the VIEW-STATE. VF manages the state of the Controller Variable in encrypted Hidden Input Field and that state is transferred to and fro to your apex controller. In Lightning, it's your responsibility to maintain state and you use Stateful Client and Stateless Server ideology. In short, you store the values you would need in aura:attribute and then transfer it later to Apex for further processing.
Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
Answer: Lightning data Services and Base Lightning Components are the lightning equivalent of VF standard controller. You cannot use VF standard controller in Lightning,
Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
Answer: Trailhead is your best friend here. It has good examples of using lightning standard controllers and how to handler events to make complex UI.
Src: https://trailhead.salesforce.com/en/content/learn/projects/workshop-lightning-programmatic/use-lightning-recordform
http://peterknolle.com/lightning-record-edit-form/
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
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%2f242135%2fhow-do-i-produce-a-new-record-button-to-look-like-a-standard-new-button%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
Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
Answer: Lightning is the way forward, Salesforce is pitching it with Blood Sweat and tears to make everyone adopt it. Building in lightning would be like futureproofing your application. The key difference between VF and lightning is the VIEW-STATE. VF manages the state of the Controller Variable in encrypted Hidden Input Field and that state is transferred to and fro to your apex controller. In Lightning, it's your responsibility to maintain state and you use Stateful Client and Stateless Server ideology. In short, you store the values you would need in aura:attribute and then transfer it later to Apex for further processing.
Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
Answer: Lightning data Services and Base Lightning Components are the lightning equivalent of VF standard controller. You cannot use VF standard controller in Lightning,
Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
Answer: Trailhead is your best friend here. It has good examples of using lightning standard controllers and how to handler events to make complex UI.
Src: https://trailhead.salesforce.com/en/content/learn/projects/workshop-lightning-programmatic/use-lightning-recordform
http://peterknolle.com/lightning-record-edit-form/
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
add a comment |
Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
Answer: Lightning is the way forward, Salesforce is pitching it with Blood Sweat and tears to make everyone adopt it. Building in lightning would be like futureproofing your application. The key difference between VF and lightning is the VIEW-STATE. VF manages the state of the Controller Variable in encrypted Hidden Input Field and that state is transferred to and fro to your apex controller. In Lightning, it's your responsibility to maintain state and you use Stateful Client and Stateless Server ideology. In short, you store the values you would need in aura:attribute and then transfer it later to Apex for further processing.
Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
Answer: Lightning data Services and Base Lightning Components are the lightning equivalent of VF standard controller. You cannot use VF standard controller in Lightning,
Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
Answer: Trailhead is your best friend here. It has good examples of using lightning standard controllers and how to handler events to make complex UI.
Src: https://trailhead.salesforce.com/en/content/learn/projects/workshop-lightning-programmatic/use-lightning-recordform
http://peterknolle.com/lightning-record-edit-form/
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
add a comment |
Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
Answer: Lightning is the way forward, Salesforce is pitching it with Blood Sweat and tears to make everyone adopt it. Building in lightning would be like futureproofing your application. The key difference between VF and lightning is the VIEW-STATE. VF manages the state of the Controller Variable in encrypted Hidden Input Field and that state is transferred to and fro to your apex controller. In Lightning, it's your responsibility to maintain state and you use Stateful Client and Stateless Server ideology. In short, you store the values you would need in aura:attribute and then transfer it later to Apex for further processing.
Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
Answer: Lightning data Services and Base Lightning Components are the lightning equivalent of VF standard controller. You cannot use VF standard controller in Lightning,
Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
Answer: Trailhead is your best friend here. It has good examples of using lightning standard controllers and how to handler events to make complex UI.
Src: https://trailhead.salesforce.com/en/content/learn/projects/workshop-lightning-programmatic/use-lightning-recordform
http://peterknolle.com/lightning-record-edit-form/
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
Should I stick with Visualforce or figure out how to create Lightning Component? What's the key differences and the future method to be using?
Answer: Lightning is the way forward, Salesforce is pitching it with Blood Sweat and tears to make everyone adopt it. Building in lightning would be like futureproofing your application. The key difference between VF and lightning is the VIEW-STATE. VF manages the state of the Controller Variable in encrypted Hidden Input Field and that state is transferred to and fro to your apex controller. In Lightning, it's your responsibility to maintain state and you use Stateful Client and Stateless Server ideology. In short, you store the values you would need in aura:attribute and then transfer it later to Apex for further processing.
Do I have to use the Lightning Data Service with Lightning Components or can I use a standard controller like in VF?
Answer: Lightning data Services and Base Lightning Components are the lightning equivalent of VF standard controller. You cannot use VF standard controller in Lightning,
Any clear and easy guides to follow in reference to Lightning Data Service and Javascript Handles.
Answer: Trailhead is your best friend here. It has good examples of using lightning standard controllers and how to handler events to make complex UI.
Src: https://trailhead.salesforce.com/en/content/learn/projects/workshop-lightning-programmatic/use-lightning-recordform
http://peterknolle.com/lightning-record-edit-form/
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
answered Dec 11 '18 at 13:35
Pranay Jaiswal
13.7k32351
13.7k32351
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f242135%2fhow-do-i-produce-a-new-record-button-to-look-like-a-standard-new-button%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
