MENU
An App Builder at UVC would like to prevent users from creating new records on an Account related list by overriding standard buttons. Which two should the App Builder consider before overriding standard buttons?
27 comments · newest first
ED
Edwin
11 months ago
Not sure about relocating buttons, sounds tricky.
NA
Nathalie
11 months ago
Wait, can we really hide buttons that can't be overridden?
JU
Jules
11 months ago
Yeah, I've done that before, it works!
KI
Kizzy
11 months ago
I agree, that's a solid option!
DE
Deane
11 months ago
Standard buttons can be overridden with a Visualforce page.
SA
Samuel
12 months ago
I’m uncertain about the specifics, but I think standard buttons can be changed in list views and search results too, right?
JA
James
12 months ago
I feel like we practiced a question similar to this, and I recall that relocating and relabeling buttons is possible, but I can't remember the details.
RO
Rolland
1 year ago
I think we discussed that some standard buttons can be hidden on page layouts even if they can't be overridden. That might be relevant here.
HA
Hana
1 year ago
I remember something about standard buttons being overridden with Visualforce pages, but I'm not sure if that's the only option.
WI
Winfred
1 year ago
I'm pretty confident on this one. The key is to look for the options that mention overriding standard buttons, which are B and D. I think those are the two correct answers.
GL
Glory
1 year ago
Okay, I've got this. The two things the App Builder should consider are that standard buttons can be overridden with a Visualforce page (option B) and that standard buttons can be overridden, relocated on the detail page, and relabeled (option D).
CH
Charlene
1 year ago
Hmm, I'm a bit unsure about this one. I know we can override standard buttons, but I'm not sure about the specific details. I'll need to think this through carefully.
CH
Chauncey
1 year ago
This question seems straightforward. I think the key is to focus on the options that specifically mention overriding standard buttons.
JA
Janessa
2 years ago
I also think option D) Standard buttons can be overridden, relocated on the detail page, and relabeled could be a good choice. It gives more flexibility in customizing the user experience.
JA
James
2 years ago
I agree with Ettie. Overriding standard buttons with a Visualforce page seems like the best option to prevent users from creating new records on an Account related list.
KI
Kirk
2 years ago
Hiding standard buttons? That's like trying to hide the fact that I forgot to do my homework. I'm going with B and D, the dynamic duo of app building!
AD
Adolph
1 year ago
A) Standard buttons can be changed on lookup dialogs, list views, and search result layouts
SE
Serina
1 year ago
C) Standard buttons that are not available for overrides can still be hidden on page layouts
CH
Charlena
1 year ago
D) Standard buttons can be overridden, relocated on the detail page, and relabeled
FL
Fletcher
1 year ago
B) Standard buttons can be overridden with a Visualforce page
SH
Shalon
2 years ago
Overriding standard buttons? Sounds like a job for a superhero app builder! B and D are my picks, but I hope they have a strong caffeine addiction to power through this.
AR
Arlyne
2 years ago
Ah, the age-old battle of standard vs. custom. I vote for B and D - let's make this app builder's life a little easier!
BU
Buffy
2 years ago
D) Standard buttons can be overridden, relocated on the detail page, and relabeled
GR
Gracie
2 years ago
B) Standard buttons can be overridden with a Visualforce page
ET
Ettie
2 years ago
I think the App Builder should consider option B) Standard buttons can be overridden with a Visualforce page.
GR
Gregg
2 years ago
Hmm, I'm not sure about hiding standard buttons. Wouldn't that just confuse users? I'd go with B and D to keep things more transparent.
DE
Derick
2 years ago
I think overriding standard buttons is a great way to customize the user experience. Option B and D seem like the best choices here.