Timeline for How do you handle deployment of changes unsupported in metadata api?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2020 at 2:23 | comment | added | David Reed | (Disclaimer: while I am a Salesforce employee, I do not know a lot about the internal history of the Metadata API. My experience is primarily as an "internal ISV".) | |
| Jun 2, 2020 at 2:00 | comment | added | Andy Ray | Makes sense. Getting to a solid development workflow in Salesforce has so many painful pitfalls, I'm always curious about the history of it | |
| Jun 2, 2020 at 1:39 | comment | added | David Reed | @AndyRay There's still some features that are either left behind in the Metadata API or so deeply entwined with org-wide setup that they're not supported. Robot/Selenium makes it possible to script setting up those features with browser automation when they're not otherwise API-accessible. | |
| Jun 2, 2020 at 1:36 | comment | added | Andy Ray | Interesting. Why do you have to resort to tools like this instead of having a first class API? Is it due to dealing with long standing Salesforce features? | |
| Apr 2, 2020 at 7:23 | vote | accept | dac1n | ||
| Mar 31, 2020 at 20:07 | comment | added | identigral | We also use a Selenium-based approach for our customers. This is the way (tm). There are a ton of tools | |
| Mar 31, 2020 at 18:38 | history | answered | David Reed | CC BY-SA 4.0 |