Timeline for Can I get this custom grid to work on Pro Edition?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2013 at 3:57 | comment | added | Rosh | sfdcfox, I've added pictures to the question so it is better understood. Let me know what's on your mind. Thanks. | |
| Jul 11, 2013 at 3:47 | comment | added | Rosh | I don't think I explained myself clearly enough. My contacts page has a simple inline VF component, which is a 6 x 8 grid. When I use {!saveRecord}, the 6 x 8 grid reloads with updated user input entered thru checkboxes. This is a simple requirement accomplished with a VF page and an extension controller that defines a custom Apex class. On the other hand, when I use standard {!save}, the 6 x 8 grid (which covers like 5% of the contacts page) is replaced with the whole contacts page itself. Please let me know if this makes sense and why I can't use {!save} | |
| Jul 11, 2013 at 3:26 | comment | added | sfdcfox♦ | Not sure you can accomplish that much. You'd be better off making it a button that the users can click to edit that info, so when they save it goes back to the page. | |
| Jul 11, 2013 at 3:19 | comment | added | Rosh | Since my requirement is for an inline VF component on the Contacts page, when I invoke {!save}, the entire Contacts page gets loaded in the small section that is actually meant only for the grid (entire Contacts page replaces the grid). And if, in that inline VF component (which is actually the entire Contacts page instead of the grid alone), I again trigger {!save} by clicking a checkbox, I see the whole Contacts page loaded again in the second-level (undesired) inline VF component - page within page within page! Hence the custom save method to load JUST the grid. Please share thoughts. | |
| Jul 11, 2013 at 2:49 | history | edited | Matt Lacey♦ | CC BY-SA 3.0 |
added 12 characters in body
|
| Jul 11, 2013 at 2:45 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |