Unlocked Packages

Package Bundles (Developer Preview) 

We are excited to announce the launch of the Developer Preview of Package Bundles! 

Package Bundles enables Salesforce partners and customers to develop, install, upgrade, and manage multiple managed second-generation packages (2GPs) and unlocked packages as if they were a single unit.  

Please fill out this short form if you would like to participate in the Developer Preview. Your participation and feedback is deeply appreciated! Thank You! 

I'm trying to package and Enhanced LWR Experience Cloud Site, and I can see DigitalExperienceBundle is actually supported according to the Metadata Coverage Report. However, I'm still getting some errors on dependent metadata while trying to package it:

site/My_LWR1: Packaging is not supported for site workspaces

I couldn't really find any official documentation on whether this is supported (neither could Claude 😅). 

Anyone having an official answer on this ? 

Thank you ! 

cc

Unlocked packages need to post install and uninstall scripts just like 2GPs do

.  Is there any scenario where these features will be brought to unlocked packages? 

2GP packages have some great features we could use in our ULPs:

1. postInstallScript
2. uninstallScript
3. postInstallUrl
4. releaseNotesUrl

Because of the limitations uninstalling ULPs (permissions sets, active flows, etc.) having the ability to perform some cleanup might help. 

Heck, I can't even get rid of an LWC property without tripping over an error, "You can’t remove the following public properties: <propertyName/>, because the component is part of a managed package," when it is part of my unlocked package.  To get around it I need to either ignore the field and keep it forever, rename it?, or uninstall/reinstall the package.

Feature Requests for Trailforce, Environment Hub and Scratch Orgs

Hello Salesforce Trailblazers,

I would love to hear from you on what's working and not working when it comes to:

• Environment Hub
• Trialforce
• Scratch Orgs
• General Environment Management in Salesforce

Where would you like us to invest and why, when it comes to managing your Environments? Please post here with your thoughts and suggestions.

If you would like to talk to me, please ping me (dburki@salesforce.com) and I would love to set up some time to talk to you. Thank you!

In my case, unlocked package B already has dependencies on packages C and D and its package version created fine. 

I then tried creating package A with a dependencies on B, C , and D.  The dependencies on C and D are identical between A's and B's sfdx-project.json. 

And yes... all these packages are sharing the same devhub

Create version status: Error
Error (MultipleErrorsError): Multiple errors occurred: 
(1) An error occurred while trying to install a package dependency, ID 04xxx00000Bxxxx: The package you're installing depends on package 'C', version '3.0'. Install package 'C' in the target org before you install package 'B'.
(2) An error occurred while trying to install a package dependency, ID 04xxx00000Bxxxx: The package you're installing depends on package 'D', version '3.0'. Install package 'D' in the target org before you install package 'B'.

Have you figured out how to enable slack in your scratch orgs?   

Recently I started seeing announcements when I logged in to our production org that Slack is now included with Salesforce.  Since we are not a current Slack customer we thought it would be interesting to see what it looks like inside a scratch org., However, I didn't notice any slack features or settings in the current documentation for building and configuring scratch orgs. 

Scratch Org Features

Scratch Org Settings

When creating a new package version for one path, why are profiles from another path included? 

1. My sfdx-project.json has two package directories, "force-app" and "mga"
2. force-app is unpackaged
3. mga is 
4. when I try creating a package version for mga, I get an errors for each profile in force-app/main/default/profiles complaining the profile, "..was named in package.xml, but was not found in zipped directory"

I don't want profiles from force-app to be included in mga's package.  I don't want anything from force-app included.  And why does it only complain about the profiles?  There are over 10000 files over there I want to ignore. 

Has anyone else seen this craziness?

I've created a new package version for omnistudio components and it should have included both an integration procedure and a data transform, but only the transform made it.   

Both files are in `omnistudio/main/default/` directory in their respective directories, `omniIntegrationProcedures` and `omniDataTransforms`. 

Have you had any luck? 

@Unlocked Packages

Package Bundles (Developer Preview) 

We are excited to announce the launch of the Developer Preview of Package Bundles! 

Package Bundles enables Salesforce partners and customers to develop, install, upgrade, and manage multiple managed second-generation packages (2GPs) and unlocked packages as if they were a single unit.  

Please fill out this short form if you would like to participate in the Developer Preview. Your participation and feedback is deeply appreciated! Thank You! 

 @Unlocked Packages