With Org Dependent packages, you can now make the set of changes dependent on the Org metadata therefore you don’t need to include the additional metadata. Let’s say you have built a new Onboarding process using Flow – now this solution needs access to a handful of standard and custom objects to operate. With Org-Dependent Packages, you are now able to make the package dependent on Org metadata rather than another or multiple packages – how cool is that? Let’s say you have some developers writing some Apex or creating Flows – now everything has a dependency on something no matter how clever you are. There is no single or yet perfect strategy for this only don’t give up. One of the challenges is untangling the happy soap, when you have loads of customisations and some big mainstream apps like Financialforce, CPQ or Not-for-profit Success Pack floating in your Org.
I’ve managed to get going on a couple of greenfield projects, but the resistant to mainstream adoption is how to do that with a complex and mature org. It’s fair to say this transition is hard and not accessible for large majority of Salesforce community.
Closing note, I just hope “FlexiPages” doesn’t become the new “Profile” for those who have been scared by metadata deployments!Īs well as optimising my development experience in VSCode, I’ve been getting down with Second-Generation Packaging and Unlocked Packages. If you can organise fields on forms – the “Page Layout” fades away…Īs well as this, there’s a ton of benefits and opportunities here beyond the obvious administration & simplification of layouts to less-is-more and only show what you need, when you need it.ĭon’t get too excited yet, this is Preview Non-GA only and limited to Custom Objects. Well this is the start of transitioning away from that. It meant functionality could be surfaced for the business when needed.ĭynamic forms extends this component visibility functionality to a field-level – now the bigger picture and story here is this – remember “Page Layouts” you know the thing they shoehorned into Lightning.
This time precision focused post, no messing only the things which have the potential to change the world (well your Salesforce world), but who knows…Īfter the introduction of “Component Visibility” we started to see the big picture and power of the Lightning App Builder, the ability to show/hide components on Lightning Pages was a turning point for driving adoption with the Lightning Platform. Nobody can blame you for feeling this way, so here we’re to brighten up your Summer and offer a slice of normality – a brand new Salesforce release and this one is difficult to simply go unnoticed. And now Summer Holidays feels much like the last 6 months… How mad is that? Summer holidays have arrived now, but who noticed? The days have blended into weeks and the weeks into months.