D B

@WadeWegner @digitalocean Huge congrats @WadeWegner

I'm thrilled to share that I've joined @DigitalOcean as Chief Ecosystem and Growth Officer! 🚀 DigitalOcean has always been about making powerful tools accessible to developers and startups. As AI transforms the landscape, that mission is more critical than ever. My goal is to ensure DO is at the forefront of this shift, providing the simplicity and predictability developers need to innovate in the AI era. 💙

@PhilW_SF I really don't know who owns that feature. If you can log a case and send me the case number, or post in a Trailblazer community post and at-mention me, I can try and find the right folks from the feature team.

@burki_db just wondering how come we can package PlatformEventSubscriberConfig with a user reference when that user won't be compatible with the subscriber org...? #mdc_platform_event_subscriber_config" target="_blank" rel="nofollow noopener">developer.salesforce.com/docs/atlas.en-…

If you're a @Salesforce @AppExchange Partner heading to #DF23 don't miss @burki_db and me sharing how to innovate faster with second-generation packages. Pssst! Our tips apply to 1GP developers, too!🤯

Posting again because I failed to make the survey accessible to everyone, so sorry! Your feedback is requested on Sandbox data seeding, please participate in our survey: forms.gle/SFC5BoHuiv7JLU…

We want to hear from you! We are designing a data-seeding solution for Sandboxes and want your opinions. Please take our survey: forms.gle/GZH7dxfJrY4Fiu…

@PhilW_SF @VivekMChawla I was not aware of this. Can you post in the Managed Packages partner community group with the specific issue you are running into, and I can see what we can do to look into this.

@burki_db @VivekMChawla are you guys aware that we cannot patch packaged flows (at least for 1GPs). This is a major limitation in adopting use of this metadata type that we were not aware of before starting to use it... :(

@PhilW_SF @kranzforce Let me take this to the team and figure out how we can document and articulate package vs namespace based limits. I can see the points you are making, I just don’t have full visibility intl those limits so have to do some homework before I get back to you

@burki_db, @kranzforce raised an interesting Q on SFXD: do uncertified managed (or unlocked) packages in the same namespace as a certified managed package benefit from the package's limits or take from the subscriber org limits?

@PhilW_SF @kranzforce Can you give me an example of a limit that you have in mind?

@HemantShukla89 @msrivastav13 @VivekMChawla It has been GA for a long time

@burki_db @msrivastav13 @VivekMChawla As org dependent unlocked package is still in beta, are there any org who are using it to untangle their production org? Also, how are they managing the fact that Apex tests are ignored for those who are part of package? #asksalesforce

The Salesforce Research & Insights team is looking to speak to developers and admins with experience with DevOps on the Salesforce platform. If you’re interested in participating, please fill out this form surveymonkey.com/r/VNM6WQ6?id=[…]. If selected you will receive a $75 e-gift card.

@muchavie @brianmfear @PhilW_SF @azlus @ImJohnMDaniel @rsoesemann @rakremi @SalesforceArchs @SalesforceDevs [2 of 2] (b) upgrade pkgA in the org to this version and select the upgrade type to be deprecate only. This ensures that the metadata is not deleted. (c) create pkgB with metadata that was removed from pkgA. Install it in the org.

@muchavie @brianmfear @PhilW_SF @azlus @ImJohnMDaniel @rsoesemann @rakremi @SalesforceArchs @SalesforceDevs [1 of 2] @muchavie - Did you try this to move metadata from one unlocked package to another? (a) remove unwanted metadata from pkgA and create a new version.

Completely agree w/@rsoesemann on this. @rakremi and @azlus have done an amazing job detailing the principles of how to compose enterprise class applications. So many good nuggets of information here and definitely worth every @SalesforceArchs and @SalesforceDevs time. #DF22

@muchavie @brianmfear @PhilW_SF @azlus @ImJohnMDaniel @rsoesemann @rakremi @SalesforceArchs @SalesforceDevs @brianmfear - as you said, for unlocked packages, during package upgrade, you can choose the "deprecate only" mode where all the metadata is deprecated. This helps in metadata movement scenario. Also agree that the FAQ is outdated :-(

@muchavie @brianmfear @PhilW_SF @azlus @ImJohnMDaniel @rsoesemann @rakremi @SalesforceArchs @SalesforceDevs @PhilW_SF - it is possible to move metadata from one unlocked package to another, & to move metadata from unpackaged to packaged state and the other way around. Moving metadata from one 2GP to another is not possible, we're thinking about how to do that, still in ideation stage.

@karenfidelak @FabienTaillon @rohitforce Thanks @FabienTaillon for evangelising all that we build. It is folks like you that inspire us to innovate.

@FabienTaillon @burki_db @rohitforce So great seeing you!

Dreamforce is over but memories keep flowing. It was great to meet again with part of the team that started SFDX, @burki_db, @karenfidelak and @rohitforce. Great times ! #DF22

@rsoesemann @VivekMChawla @AquivaLabs @ch_sz_knapp That’s right Robert. This is mainly to address uncommon but strategic scenarios like a company selling a part of their portfolio resulting in this use case. It also helps in scenarios where a genuine mistake occurred and the package was associated with the wrong dev hub.

@VivekMChawla @AquivaLabs @burki_db @ch_sz_knapp So @VivekMChawla are you saying that we as PDO should never create a customer package from our own DevHub. Even if there is this transition feature now?

Great #df22 news for PDO partners like @AquivaLabs: Managed Packages can now be built from a partner DevHub and later be (ownership-)transferred to the customer. Thanks, @burki_db, @VivekMChawla et al.

@dieffrei @dieffrei - I have pinged support to take a look at this.

Has anyone run into the same problem? CC: @burki_db Case #42682338

Package version creation is getting very slow. Just for reference, a package version for a smaller package that 1 year ago used to take around 2-5 minutes(with code coverage calculation), now is taking 41 minutes. Other packages are taking 4..5 hours to complete @SalesforceDevs

@azlus @rohitforce @azlus - I have pinged support to investigate and escalate it to engineering if they need help.

@rohitforce @burki_db Another one #42580763

Package Creation and Scratch Orgs and even deployment to sandboxes have been basically dead for the past two days with multiple errors. Come on Salesforce these are really critical lnkd.in/e4h2dHGg

Want to manage your application’s lifecycles at lightning speed? ⚡️ Join us May 11, at 11 a.m. PT / 2 p.m. ET, and learn ALM best practices that give developers the power to create and innovate with peace of mind. Get in the know: sforce.co/3MSugJ4

@eugenevab @VivekMChawla @rsoesemann @appexchange @VivekMChawla - we should take this to the feature team to see how they can prioritize this.

@VivekMChawla @rsoesemann @appexchange @burki_db that is sad :( How can we provide a guidance for customers using 2nd gen packaging?

@appexchange partners don't wait for SF to technically migrate their 1GP monolith to 2GP and gradually migrate over today. I created a quite broad question to learn what worked for you and what SF (@VivekMChawla @burki_db et al.) recommends. salesforce.stackexchange.com/q/375603/256