Timeline for Using User Information to show relevant fields dynamically vs having multiple separate components
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2019 at 15:58 | vote | accept | Daniel Retaleato | ||
| Apr 5, 2019 at 17:11 | comment | added | Daniel Retaleato | Thanks for the response! We have 4-5 different divisions (ticket sales, executive suite sales, sponsorships etc) that all need to be able to add contacts to accounts. However, all divisions have different required fields and some fields are only used by one or two divisions, so our solution was to literally build a custom form with all relevant information based on profileID at runtime. Do you think we'd be able to implement CRUD and FLS permissions into our custom component? | |
| Apr 5, 2019 at 16:22 | answer | added | sfdcfox♦ | timeline score: 0 | |
| Apr 5, 2019 at 16:06 | comment | added | David Reed | What you're describing sounds, to an outsider, like the same functionality that is provided by Salesforce's native CRUD and FLS permissions system. Could you accomplish this need by checking CRUD and FLS at runtime rather than implementing multiple components? | |
| Apr 5, 2019 at 16:05 | review | First posts | |||
| Apr 5, 2019 at 19:18 | |||||
| Apr 5, 2019 at 16:02 | history | asked | Daniel Retaleato | CC BY-SA 4.0 |