Can anyone confirm if we can create managed packages in Scratch org. Of so, can please share the relevant documentation.

  • No, must be on developer org, are you working for an isv? – Raul Jul 23 '19 at 20:19
  • No.. but I have to hide my classes and other piece source code... Dev Org I knew, but I can't do in that because I don't have it corresponding to prod. And I don't want to develop in any org which don't have association to my prod org, as it needs to have my prod customizations. Hope you understand the concern... – Varun SFDC Jul 23 '19 at 20:25
  • How about 2nd generation managed Package ? – Varun SFDC Jul 23 '19 at 20:34
  • This seems like an x-y problem. If you do not work for an ISV and are building code to be deploying to a single prod environment, why do you need a managed package to provide IP protection? – David Reed Jul 23 '19 at 20:45
  • Hi David, so there are multiple stakeholders for Dev... Hence, code abstraction is being emphasized. Little confused on the approach I should be using – Varun SFDC Jul 23 '19 at 20:49

Managed packages are not a tool for code modularization and abstraction within a single production org. Managed packages are intended for ISVs to deliver their products to Salesforce customers, and come with an extensive list of benefits (including IP protection) and restrictions.

It is unclear exactly what you're being asked to do here. It may be as little as complying with enterprise design patterns that utilize separation of concerns and a layered architecture. Or, it may be that your organization plans to utilize the Package Development Model with Unlocked Packages, which you do build in a source-focused, scratch org-based development model.

You should work with your technical lead or architect to understand exactly what code architecture is being prescribed.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.