Timeline for Access Pagelayout assigned for a profile for a object using metadata api
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2019 at 16:26 | comment | added | David Reed |
@NoNicknameSFDC It's hard to provide more detail without hearing more about your use case (which is information you can edit into your question). I'm not sure why you need the page layout name alone, or why you would opt not to use <lightning:recordForm>, which does a lot of the heavy lifting for you. Adding this detail to your question can help produce more valid answers.
|
|
| May 24, 2019 at 14:49 | comment | added | NoNicknameSFDC | Going thru the example here - developer.salesforce.com/docs/atlas.en-us.uiapi.meta/uiapi/… , this works when I am building a custom UI. Even I would agree on this part. My intention is to use Lighting:EditRecordForm with fields loading automatically. Thats the intention behind. With UI API, it becomes too much of code and manual deployments in my case, which would be difficult to convince. | |
| May 24, 2019 at 14:33 | comment | added | David Reed | @NoNicknameSFDC I definitely get that, but the Metadata API is not a good solution for you. | |
| May 24, 2019 at 14:29 | comment | added | NoNicknameSFDC | I need to access the assigned PageLayout Name dynamically for the logged-in user for a given record id / object and record type. Rest of accessing the details of pagelayout is already completed. I don't want to hardcode the details of PageLayout name. | |
| May 24, 2019 at 12:42 | history | answered | David Reed | CC BY-SA 4.0 |