Timeline for Using User Information to show relevant fields dynamically vs having multiple separate components
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2019 at 15:58 | vote | accept | Daniel Retaleato | ||
| Apr 5, 2019 at 17:17 | comment | added | sfdcfox♦ | @DanielRetaleato Once you start writing your own code, you can do whatever you want. Unfortunately, this usually means losing access to standard functionality. I strongly advise that you consider removing your custom code in favor of standard features as much as possible. However, I do realize that this may not be practical depending on how much needs to be done. It is entirely possible to check field level security, object security, etc in code, but you're making a lot of extra work for yourself. Going back to standard features would probably take less time than more custom code. | |
| Apr 5, 2019 at 16:58 | comment | added | Daniel Retaleato | Thanks for the quick response. As of right now, our org is built primarily on custom code, so the framework is all there to get everything done in the background. In your opinion, will all of this be able to be implemented into our custom component? | |
| Apr 5, 2019 at 16:22 | history | answered | sfdcfox♦ | CC BY-SA 4.0 |