Timeline for Issues With Managed Package Upgrade
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2017 at 11:33 | vote | accept | Nachiket Deshpande | ||
| Oct 24, 2017 at 21:44 | answer | added | Daniel Ballinger | timeline score: 4 | |
| Oct 24, 2017 at 12:26 | history | tweeted | twitter.com/StackSalesforce/status/922801556482863104 | ||
| Oct 24, 2017 at 10:29 | comment | added | Nachiket Deshpande | @TusharSharma Agreed !! or if SF could add option to let subscriber deiced whether they want to override changes or not during package upgrade may help in such scenarios. | |
| Oct 24, 2017 at 10:24 | comment | added | Tushar Sharma | if subscriber has changed the details then your upgrade will override his changes. Thats why SF don't push your changes or let subscriber decide. | |
| Oct 24, 2017 at 9:42 | comment | added | Nachiket Deshpande | @TusharSharma yeah that was my thought as well , but if these are part of package then upgrading these changes might not affect subscriber just a thought. | |
| Oct 24, 2017 at 9:39 | comment | added | Tushar Sharma | As subscriber can change these details as well. So I think SF does not allow them to overwrite again. Thats why your changes doesn't reflect in old org. | |
| Oct 24, 2017 at 9:27 | history | asked | Nachiket Deshpande | CC BY-SA 3.0 |