Chvíli to trvalo, ale nakonec si mě pozvali i do CZPodcast. Vlastně stačilo, aby Filemon začal víc přemýšlet, zda se má vrhnout i na Salesforce a nějak jsme to dali dohromady.
Takže pro ty, co CZ Podcast neznají a tak povídání nezaregistrovali to dávám i na blog. A současně samozřejmě pro mě, ať mám někde seznam všech těch skvělých příležitostí, kdy jsem mohl šířit své rozumy 🙂
Užívejte
Napiš komentář, díky!I’m pretty sure you noticed this new certification, which is available since September 2024. I originally tried to pass it before Dreamforce but failed, but finally found time before Christmas and this time I passed.
I wasn’t alone and you’ll see on social networks even more people happily sharing their successes. No surprise as Salesforce decided to give first try of this certification for free till the end of 2025 and on top of that pushes partners to get at least 5 certified people to qualify for some extra treatment in the AI area.
Meredith put together great article with plenty of links and I would add the Einstein Cheat Sheet on top of that. There were also preparation days with Salesforce, which I didn’t attend but heard the recordings are great. See part 1 and part 2.
From my experience, there are a few areas where you really need to be strong:
Besides that there are some small bits but nothing major I would say.
What now?
Go for it! First try is for free, so no reason why not try it, obviously if you want to pass it pays off to study a bit more. The exam probably won’t really give you an answer how Prompt Builder and Einstein are different to Agentforce, but don’t worry too much about Salesforce product names and focus on what is important – the right use case, where it can really bring some benefits to the users and to the business.
Good luck!
The record-triggered flows with Custom Error element has been introduced a while back (Winter ’24 actually). I immediately saw their benefits but didn’t see many use-cases I would need them for.
The first use-case, when it was tempting, was a requirement to allow progress of opportunity into next stage only when products are added. Great use-case, but there is better OOTB functionality – the HasOpportunityLineItem which can be true or false.
But finally I got a bunch of great use-cases on current project, which are actually at the end linked together.
On account the customer has a multi-select picklist to choose industries, where the company is active. On opportunity they want to select for which specific industry it will be used. It is a single select and there is an obvious requirement for the user to be able to choose only something which is listed on the account.
Yeah, multi-select picklist, you can already smell it won’t be possible to check in validation rule. I mean it would be but you would need to list all the choices and compare, I didn’t find a way how to create a simple and universal validation rule.
Luckily, there is a before-save flow, where you can assign the multi-select into one variable and check whether it contains the value from opportunity, if not -> custom error.
Solved!
The list of the industries are fashionably long and when you are creating the opportunity you might not remember what is selected on the account. Especially if you are creating it from the menu or global action.
But hey, there is no way how you can make the picklist on opportunity dynamic, unless you want to develop it as custom component and then you have a challenge how to incorporate it nicely into the form.
Never mind, we have the flow above with the custom error and in the error we can list the industries from the account. Not a perfect solution as first save is rather a try, but on second save you know from which values you can choose.
Actually, with the right question we quickly found out that majority of accounts have just one industry. At that moment the solution was simple – in the before-save flow first check if there is only single industry, in such case set the industry on opportunity. If there are multiple check whether they selected the right one and if not give them a help text with suggestions what they can use.
Historically we would use something like DLRS to count the number of future activities linked to opportunity and build a validation rule linked to that field. Which would mean daily recalculation of all opportunities and other ugly things.
Luckily, before-save flow, which triggers when Stage is changed, query related activities with future date and if the collection is empty shows the custom error.
Similarly you can check whether this is first opportunity or another for the account and set/require the right type of opportunity.
What started as super unhappy customer quickly iterated to something pretty usable what the customer is willing to accept as a nice solution. Thank you Salesforce and especially the Flow team for extending the platform with such goodies!
Napiš komentář, díky!At Actum we have Salesforce and Microsoft division, which gives us the unique benefit of being able to propose CRM solutions on both platform (actually we can do SAP as well). It also means that Salesforce isn’t really happy and I’m not sure about Microsoft.
Anyway, the other day we have been preparing with Karel (the Delivery Director of Microsoft division) another RFP, where customer wanted quotation for both platforms and Karel wasn’t really happy with the estimates I’ve been putting together. The idea has been born – let’s compare the solutions side by side.
It took a bit longer to prepare everything, after all the summer period is usually a bit slower and we’ve been busy on projects. At the end of summer Adam (the Kentico Division Director) agreed to be our customer and put together his requirements for CRM system, based on which we should configure the systems live from scratch.
Beginning of September roughly 50 people have been registered for the event, majority of them attended on-site and we had a few on-line people as well. The start of the event was a bit stresful as the meeting room got cleared just minutes before start, we didn’t have time to test the beamers (they don’t really work on black wall) and a few other things, but at the end we started basically on time.
As I’ve been presenting I didn’t really have time to pay close attention to what Karel is doing, from my point of view the solutions are almost equal, each of them has their own benefits which you might or might not appreciate. A feedback I’ve got after the event was, that it feels like you need to click more on Microsoft to set it up and Karel had a bit challenge to keep up with me configuring the system. But that’s not something you’ll really appreciate in daily live.
At the end Adam as our jury decided it was a tie with each platform being slightly better at some areas but generally speaking both were really good. Obviously the sample scenario was super easy, at the same time what we see in real life customers aren’t usually more complex as the platforms bring most of the features out of the box.
It also looks like an important event for the wider community as potential customers are still getting in touch with us asking for recording or whether we can run it for them again. And we are definitelly happy to help with finding the right solution, our System Integration division can run technology agnostic discovery of needs and at the end compare the solutions and clearly say why they propose one of them, including TCO calculation.
Slighly selling end, but it happens and I really enjoyed this event. Does it make sense to compare Teams and Slack or who cares?
Napiš komentář, díky!
Magic happened over the weekend and most of my customers got a new version of their Salesforce. This time I was prepared as I read the release notes on my way to Dreamforce – what a great reading for long flight!
