Timeline for Can DeveloperName Be Updated via Apex Metadata API in a Custom Metadata Type?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2019 at 4:26 | vote | accept | FixxzerOfShiite | ||
| Oct 18, 2019 at 21:30 | comment | added | Avrom Roy-Faderman | Basically, you can't update that field because, from the perspective of the Apex MD API (or the regular MD API, for that matter), developer name (together with namespace) is used to identify what record you're talking about. If you change the name, it has no way of knowing that you mean the original record. | |
| Oct 18, 2019 at 21:28 | comment | added | Avrom Roy-Faderman | In general, I really don't recommend using the DeveloperName field for anything but identifying the record. | |
| Oct 18, 2019 at 15:29 | comment | added | FixxzerOfShiite | I guess it can't be changed. Unfortunately, "DeveloperName" was the field I was relying on to set Mule environments. Any hopes of writing post deployment scripts to set this field to the correct setting is now gone. I have to flip this to custom settings now and change it in 30 different places. | |
| Oct 17, 2019 at 18:33 | comment | added | FixxzerOfShiite | Except, I've found you can certainly update other fields using Apex Metadata API. Just haven't figured out if there's a way to update the "DeveloperName" field. Use this: sfdcpanther.com/create-update-custom-metadata-using-apex and this: corevalue.net/deploying-custom-metadata-records-apex-code for reference. | |
| Oct 17, 2019 at 2:47 | history | answered | Avrom Roy-Faderman | CC BY-SA 4.0 |