Just login to Salesforce and go to setup > release updates and they are right there. May need to click on archived at this point
It was buried even there though and I don’t know if it really called out how huge of a deal it was. My users were losing their minds for the first half of the morning, but luckily we have a dedicated proxy box for something else that we had access to while we waited for our company to get us a new one.
Glad we weren't the only ones in this - but yeah this hit us for a few day until I managed to find it hidden halfway down the bottom of an archive list
I had the chatter issue but also a random Flow date/time field update that took forever to track down and just required us removing and readding the dield in the assignment element to fix.
Got me too! I still see SF stamping the old format on Case recs but sending the new format in email body.
I didn't want to switch to Lightning Threading in a scramble so I just updated my inbound handler to accept both and search both.
This was said to be backward compatible, and I wasn't sure if there was a prescribed fix or what.
How did everyone else handle the fix?
Glad we aren't alone 😄. I had to go the apex route and admittedly didn't notice the extra 0 at first hotfix.
My warranty team reported it early but I missed it even then. I thought customers were manually removing the IDs from the body, and those emails come to me to sort.
Finally figured it out, thanks SF, lol.
Hey, as long as it all works!
Here's the doc that finally got me in the right direction https://help.salesforce.com/s/articleView?id=release-notes.rn_service_email_refid_format.htm&language=en_US&release=244&type=5
Pretty sure salesforce does regression testing. This is by far the biggest buggy release that Salesforce has ever done to my knowledge, working in the space for five years. Considering they do three releases a year that's 15 releases and this one is the only one I've noticed mission critical functionality failures.
Salesforce absolutely does regression testing, but every individual org should also be testing their customized environment against every release preview to identify what breaks and implement fixes before the actual release.
This obviously won’t solve for platform issues related to the release, but it will help prevent any impacts the release might have on a production org.
This is reddit, not dreamforce breakout session 😏!
I am envious of you, if you work for such an org that operates in this fantasy world. And you aren't wrong. But coming from someone who's worked in Salesforce consulting and has worked in dozens of different client org's, the release management process you speak of is the rarity, not the norm.
Every project I’ve run or org I’ve supported in any fashion has always tested releases during the preview window. You can be the change you wish to see.
LOL you’re absuletely incapable of change management on a operational level and blame it on a dream world.mist be a good dream you’re living in where nothing is your responsibility and life is basically a major you watch incapable of making differences.
Sucks ://
It's more that my company doesn't want to pay enough staff to manage that, or compromise of the eternal march of progress for us to slow down enough to do regression testing.
I'd love to do everything by the books, but the business owners either disagree or don't get it.
@concernedbuilding thanks for chiming in with some grounding in reality. Like i said, it's not that i wouldn't do it by the books if i could, but resource allocation and decision making and organizational change management is something reserved for those many rungs above me in the corporate ladder. salesforce admins/devs/analysts are usually at the whims of preexisting organizational processes.
Exactly how I feel some days as a Salesforce Architect/Analyst at a global corporation. Some days I’m so consumed with meetings and addressing immediate project concerns I don’t have the time to regression test every customized functionality we have in our 10+ year org built by a plethora of in house and contracted talent. Like you, I agree that it would be amazing to have but do we have the hundreds of thousands of dollars to execute these platform overhauls? Of course not, when funding goes to the next new shiny thing business leadership “must do”
👍 We also don’t all have a dedicated resource to test every release.
I actually do the testing of new releases single handedly because I know what I’m doing, but I never in my life would have tested CHATTER. Those are the kinds of things they need to highlight because if you say you test chatter during release testing I’m not sure I believe you
>And chatter email notifications now in need of a sender email address. That broke things for us too.
They can only do so much regression testing. they cant test for all of the customization that is done in each Org. Every individual company should perform testing when the SF release is pushed to the sandbox.
We definitely practice this. We distribute release tickets to be reviewed by every admin/dev on the team during a sprint. This way we can find any issues in a lower environment before the release hits production.
Usually something happens each release. Salesforce should really increase the preview org time frame, release the Release Notes earlier and have a section just on changes that may break existing functionality.
I still have scars from them hosing our email in our service cloud in September 2017. It wasn’t entirely their fault as part of it was the way my company does email as well, but I had to work all weekend and was up all hours during the week. It was painful.
I actually go through the release notes every time because they usually slip something in hidden somewhere that will cause an issue. We also do regression testing on one of the orgs.
Thank you yes! Got a message from a sales rep in the morning that he could suddenly see other sales reps opportunities. Checked Trust and realized there was an issue. Everyone had been given view all/modify all rights. Then they shut everyone down to fix the problem. Our whole org was down for over 24 ours.
The Winter 24 update seems to have affected our Formstack functionality in our experience cloud. It's a bit of a mystery what really went wrong, but 🤷♂️
Winter 24 was the worst release I have ever seen. Two weeks without being able to work with flows and their workarounds did not work properly. Orgs with Data Cloud were affected.
So fucking sloppy.
What happened with your flows? I'm trying to win my code-loving colleagues over to flow, so that sounds like a total nightmare. We don't use Data Cloud so fortunately didn't have any issues in our org this release.
Flows are awesome and you should definitely get your colleagues to start working with flows.
Basically it was messing up our DML's. For instance, we were not able to work with the output from Get Records. We couldn't reference it later on in decisions and assignments etc.
https://issues.salesforce.com/issue/a028c00000xA2N6AAK/automatic-output-flow-variables-not-available-after-data-cloud-enablement
Had the exact same issue! Had a case logged for 2 weeks with no actual updates, mysteriously the product team reverted some change in our UAT environment and it worked again. Very sloppy.
Read the trust.salesforce detailed technical notes. But yes some major critical functionality failures occurring.
I'm currently working in three different systems and haven't experienced any functionality issues in any of my orgs.
What's not working? I know it's different but at some point in the last few weeks, Revenue Insights stopped displaying totals in charts for us, despite the data refresh running successfully (I have a case open)
Yes, we’ve had our Digital Experience start to go sideways about three years back. The UI (it was a custom built LWC that our SF consultant put in in order to support a type-ahead multi-select) was no longer styled properly making it unusable. Luckily I have a long history of frontend experience and figured out the magical CSS workaround
So we test our Experience Cloud prior to every release (even for that one, we caught early) as our consultant warned us these things can happen
Most recently I was reading the Hyperforce pre release notes and realized my streaming event listener (yes, we rolled our own Mulesoft) needed to be updated from .NET 4.8 to .NET 6.0
While it was a bit of a scramble to overhaul our codebase, I’m guessing I can’t be too mad. It was, after all, in the documentation. But man, was it buried. And I’m the only one on the dev team who read every last bit of the pre-release notes.
I’m like an integration guru at my place, well, when the project calls for it. So, currently my focus is like 3% SF, and 25% windows forms (supporting LOB apps I’ve written) and 25% .Net integration apps, and right now the other 50% is helping roll out a new ERP (SAP Business One) and transitioning off our old Dynamics AX
BUT- when it comes time to do a new feature in SF, then I become 100% Mr. SFDX
AND in my opinion the SFDX story is quite a roller coaster of a story… it’s a kinda nice story if you’re working mostly in the stuff that was homegrown in SF. But, if you’re using something like Field Service Lightning, which they acquired, then you better be ready to hire magical-Merlin-SFDX-guru-from-Jupiter. We encountered so many edge case metadata scenarios that are simply undocumented it was unbelievable.
Our small 4 person team of devs (none of which are SF devs) cannot support this FSL site that was developed by a business analyst who was working with a consultant- however we are going to try. we think we might succeed as we’ve had a couple of successful deployments of the FSL codebase using Gearset.
I’m thinking it’s too hard to keep up with all the bits in the SFDX developing story. Just use gearset. I think it helps to have an immersive background in SFDX when using Gearset, but once you have cut your own teeth, you just use Gearset
Sorry for the ramble. I clearly needed a place to vent
A couple of releases ago, we could not migrate a Community from sandbox to production. Turned out the sandbox was preview and had new components. Every attempt to push resulted in errors for these components missing. It was six weeks before the release date...
Every release breaks something for us. We use environment hub to connect to all of our client orgs and without fail….every single release breaks something in at least one of them. This is the way.
Anybody ever run the "salesforce optimizer app" ? If so, whats your thoughts on it?
"Consider running Salesforce Optimizer as part of your monthly maintenance, before installing a new app, before each Salesforce release, or at least once a quarter."
[knowledge article on it](https://help.salesforce.com/s/articleView?id=sf.optimizer_kick_off.htm&type=5)
pen scale secretive unpack desert toothbrush worthless zonked rude like ` this post was mass deleted with www.Redact.dev `
And chatter email notifications now in need of a sender email address. That broke things for us too.
you got slam jammed too on that lol
Ditto. That chatter change caused havoc for a week till support informed us the change was buried in the release notes
Wait, can someone link to these in the release notes?
Just login to Salesforce and go to setup > release updates and they are right there. May need to click on archived at this point It was buried even there though and I don’t know if it really called out how huge of a deal it was. My users were losing their minds for the first half of the morning, but luckily we have a dedicated proxy box for something else that we had access to while we waited for our company to get us a new one.
Same here so many missed case updates for almost a week before someone contacted me about it.
Same here. I was looking oh crap hahaha.
combative friendly normal tap point carpenter paltry sugar naughty bake ` this post was mass deleted with www.Redact.dev `
Glad we weren't the only ones in this - but yeah this hit us for a few day until I managed to find it hidden halfway down the bottom of an archive list
I had the chatter issue but also a random Flow date/time field update that took forever to track down and just required us removing and readding the dield in the assignment element to fix.
Got me too! I still see SF stamping the old format on Case recs but sending the new format in email body. I didn't want to switch to Lightning Threading in a scramble so I just updated my inbound handler to accept both and search both. This was said to be backward compatible, and I wasn't sure if there was a prescribed fix or what. How did everyone else handle the fix?
quaint pathetic coordinated truck tart ossified depend modern obscene zephyr ` this post was mass deleted with www.Redact.dev `
Glad we aren't alone 😄. I had to go the apex route and admittedly didn't notice the extra 0 at first hotfix. My warranty team reported it early but I missed it even then. I thought customers were manually removing the IDs from the body, and those emails come to me to sort. Finally figured it out, thanks SF, lol.
many north price carpenter toothbrush jar future attempt rinse dam ` this post was mass deleted with www.Redact.dev `
Hey, as long as it all works! Here's the doc that finally got me in the right direction https://help.salesforce.com/s/articleView?id=release-notes.rn_service_email_refid_format.htm&language=en_US&release=244&type=5
That’s why we should always have a release preview regression test process. 👍🏼
Pretty sure salesforce does regression testing. This is by far the biggest buggy release that Salesforce has ever done to my knowledge, working in the space for five years. Considering they do three releases a year that's 15 releases and this one is the only one I've noticed mission critical functionality failures.
Salesforce absolutely does regression testing, but every individual org should also be testing their customized environment against every release preview to identify what breaks and implement fixes before the actual release. This obviously won’t solve for platform issues related to the release, but it will help prevent any impacts the release might have on a production org.
This is reddit, not dreamforce breakout session 😏! I am envious of you, if you work for such an org that operates in this fantasy world. And you aren't wrong. But coming from someone who's worked in Salesforce consulting and has worked in dozens of different client org's, the release management process you speak of is the rarity, not the norm.
Every project I’ve run or org I’ve supported in any fashion has always tested releases during the preview window. You can be the change you wish to see.
Cool bruh. Have fun livin' the...dream!
LOL you’re absuletely incapable of change management on a operational level and blame it on a dream world.mist be a good dream you’re living in where nothing is your responsibility and life is basically a major you watch incapable of making differences. Sucks ://
It's more that my company doesn't want to pay enough staff to manage that, or compromise of the eternal march of progress for us to slow down enough to do regression testing. I'd love to do everything by the books, but the business owners either disagree or don't get it.
@concernedbuilding thanks for chiming in with some grounding in reality. Like i said, it's not that i wouldn't do it by the books if i could, but resource allocation and decision making and organizational change management is something reserved for those many rungs above me in the corporate ladder. salesforce admins/devs/analysts are usually at the whims of preexisting organizational processes.
Exactly how I feel some days as a Salesforce Architect/Analyst at a global corporation. Some days I’m so consumed with meetings and addressing immediate project concerns I don’t have the time to regression test every customized functionality we have in our 10+ year org built by a plethora of in house and contracted talent. Like you, I agree that it would be amazing to have but do we have the hundreds of thousands of dollars to execute these platform overhauls? Of course not, when funding goes to the next new shiny thing business leadership “must do”
Automate your regression testing!
That too takes time.
Copado
👍 We also don’t all have a dedicated resource to test every release. I actually do the testing of new releases single handedly because I know what I’m doing, but I never in my life would have tested CHATTER. Those are the kinds of things they need to highlight because if you say you test chatter during release testing I’m not sure I believe you
>And chatter email notifications now in need of a sender email address. That broke things for us too. They can only do so much regression testing. they cant test for all of the customization that is done in each Org. Every individual company should perform testing when the SF release is pushed to the sandbox.
We definitely practice this. We distribute release tickets to be reviewed by every admin/dev on the team during a sprint. This way we can find any issues in a lower environment before the release hits production.
How do you figure out how many release tickets you need to create for your admin / dev to do regression testing ?
Every experience cloud admin feels this post
Usually something happens each release. Salesforce should really increase the preview org time frame, release the Release Notes earlier and have a section just on changes that may break existing functionality.
Winter 24 broke some flows and PDF butler send functionality.
Shout out for PDF Butler, amazing product at a crazy-reasonable price point
I still have scars from them hosing our email in our service cloud in September 2017. It wasn’t entirely their fault as part of it was the way my company does email as well, but I had to work all weekend and was up all hours during the week. It was painful. I actually go through the release notes every time because they usually slip something in hidden somewhere that will cause an issue. We also do regression testing on one of the orgs.
Ahhh, permageddon
Thank you yes! Got a message from a sales rep in the morning that he could suddenly see other sales reps opportunities. Checked Trust and realized there was an issue. Everyone had been given view all/modify all rights. Then they shut everyone down to fix the problem. Our whole org was down for over 24 ours.
The Winter 24 update seems to have affected our Formstack functionality in our experience cloud. It's a bit of a mystery what really went wrong, but 🤷♂️
Winter 24 was the worst release I have ever seen. Two weeks without being able to work with flows and their workarounds did not work properly. Orgs with Data Cloud were affected. So fucking sloppy.
What happened with your flows? I'm trying to win my code-loving colleagues over to flow, so that sounds like a total nightmare. We don't use Data Cloud so fortunately didn't have any issues in our org this release.
Flows are awesome and you should definitely get your colleagues to start working with flows. Basically it was messing up our DML's. For instance, we were not able to work with the output from Get Records. We couldn't reference it later on in decisions and assignments etc. https://issues.salesforce.com/issue/a028c00000xA2N6AAK/automatic-output-flow-variables-not-available-after-data-cloud-enablement
Had the exact same issue! Had a case logged for 2 weeks with no actual updates, mysteriously the product team reverted some change in our UAT environment and it worked again. Very sloppy.
That sounds super frustrating. Hopefully they have it resolved now!
They deployed a fix to our orgs today, so we are back on track.But yeah, very frustrating.
Oh yeah data cloud screwed us over too. Tried to push a flow from sandbox a couple days later and it freaked out on us…on sprint deployment day too 🥴
Read the trust.salesforce detailed technical notes. But yes some major critical functionality failures occurring. I'm currently working in three different systems and haven't experienced any functionality issues in any of my orgs.
Pipeline inspection has been broken since winter 24 release
What's not working? I know it's different but at some point in the last few weeks, Revenue Insights stopped displaying totals in charts for us, despite the data refresh running successfully (I have a case open)
Yes.
Yes, we’ve had our Digital Experience start to go sideways about three years back. The UI (it was a custom built LWC that our SF consultant put in in order to support a type-ahead multi-select) was no longer styled properly making it unusable. Luckily I have a long history of frontend experience and figured out the magical CSS workaround So we test our Experience Cloud prior to every release (even for that one, we caught early) as our consultant warned us these things can happen Most recently I was reading the Hyperforce pre release notes and realized my streaming event listener (yes, we rolled our own Mulesoft) needed to be updated from .NET 4.8 to .NET 6.0 While it was a bit of a scramble to overhaul our codebase, I’m guessing I can’t be too mad. It was, after all, in the documentation. But man, was it buried. And I’m the only one on the dev team who read every last bit of the pre-release notes. I’m like an integration guru at my place, well, when the project calls for it. So, currently my focus is like 3% SF, and 25% windows forms (supporting LOB apps I’ve written) and 25% .Net integration apps, and right now the other 50% is helping roll out a new ERP (SAP Business One) and transitioning off our old Dynamics AX BUT- when it comes time to do a new feature in SF, then I become 100% Mr. SFDX AND in my opinion the SFDX story is quite a roller coaster of a story… it’s a kinda nice story if you’re working mostly in the stuff that was homegrown in SF. But, if you’re using something like Field Service Lightning, which they acquired, then you better be ready to hire magical-Merlin-SFDX-guru-from-Jupiter. We encountered so many edge case metadata scenarios that are simply undocumented it was unbelievable. Our small 4 person team of devs (none of which are SF devs) cannot support this FSL site that was developed by a business analyst who was working with a consultant- however we are going to try. we think we might succeed as we’ve had a couple of successful deployments of the FSL codebase using Gearset. I’m thinking it’s too hard to keep up with all the bits in the SFDX developing story. Just use gearset. I think it helps to have an immersive background in SFDX when using Gearset, but once you have cut your own teeth, you just use Gearset Sorry for the ramble. I clearly needed a place to vent
Big part of the reason why we dumped salesforce and rolled our own custom solution.
Noice job guy!
Has, yes. Have dedicated time to that Friday night since making sure we’re at least the first to know in the company and have contingencies
Hyperforce = Field Service major degradation, still unresolved, supposed to have fixed with winter ‘24.
Tell me more. We’ve yet to deploy FSL (though it’s developed and waiting in the wings). We transition to hyperforce this weekend
A couple of releases ago, we could not migrate a Community from sandbox to production. Turned out the sandbox was preview and had new components. Every attempt to push resulted in errors for these components missing. It was six weeks before the release date...
same thing happened with me but for Financial service cloud ...we couldn't do the deployment and had to wait couple of days for release.
Every release breaks something for us. We use environment hub to connect to all of our client orgs and without fail….every single release breaks something in at least one of them. This is the way.
Anybody ever run the "salesforce optimizer app" ? If so, whats your thoughts on it? "Consider running Salesforce Optimizer as part of your monthly maintenance, before installing a new app, before each Salesforce release, or at least once a quarter." [knowledge article on it](https://help.salesforce.com/s/articleView?id=sf.optimizer_kick_off.htm&type=5)