Skip to main content
9 events
when toggle format what by license comment
Jul 27, 2023 at 2:47 comment added MayTheSForceBeWithYou Blaming the Developer Advocate about this though is like blaming the flight attendant for the plane being delayed ¯_(ツ)_/¯
Oct 21, 2021 at 8:53 comment added wesaw Completely agree with @PhilW point. Moreover, changes that break backward compatibility should be communicated in advance (at least that what serious products are doing), so that devs can get ready by analyzing code base, preparing changes etc. It's by far not OK that we are getting to know about this error only after encounter it in practice and figuring out solution in stack overflow post(
Oct 1, 2021 at 14:00 comment added POZ You can save some time with a RegEx search and replace: twitter.com/PhilippeOzil/status/1443938580380913671
Sep 21, 2021 at 19:15 vote accept Alba Rivas
Sep 10, 2021 at 17:13 comment added Alba Rivas Thank you Phil for your feedback. The suggested workaround is: 1- Retrieve the same page using the newer API version which would generate the required identifiers for them 2 - Use this metadata to deploy using the newer API version
Sep 10, 2021 at 15:11 comment added Phil W Hey Alba, that's a PM that has no care about the number of developers who will be impacted. This sort of breaking change, though minor, will cost each developer time, wasting potentially years of "man time" across the entire developer base.
Sep 10, 2021 at 15:04 comment added Alba Rivas I've asked the PM for this area and he's confirmed there're no plans to fix this behaviour. I'm sorry!
Sep 9, 2021 at 8:37 comment added Phil W This is a breaking change by SF in that case, with no backwards compatibility, which is a very bad thing for them to do. Will this be corrected before Winter 22 GA? In addition, is this likely to impact managed packages that contain flexipages with no identifiers?
Sep 9, 2021 at 7:56 history answered Alba Rivas CC BY-SA 4.0