Timeline for Second-generation Managed Package with dependency on first-generation Managed Package
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2023 at 17:32 | comment | added | nstuyvesant | Really appreciate the help Phil W! | |
| Jan 28, 2023 at 19:26 | comment | added | Phil W | I have reached out to a Salesforce packaging expert to ask their advice. They will comment here later, with luck... | |
| Jan 28, 2023 at 18:32 | comment | added | nstuyvesant | Oh ok... the Salesforce docs really push the idea that you have to put the Connected Apps into a 1GP to reference them from an Aura Component Bundle in a 2GP... developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/… | |
| Jan 28, 2023 at 15:26 | comment | added | Phil W | I haven't used canvasApp so cannot tell you how to solve this directly. | |
| Jan 28, 2023 at 14:59 | comment | added | nstuyvesant | In our Aura Component Bundle, the force:canvasApp has a developerName attribute that's supposed to be the name of the Connected App. If the Connected App is not referenced anywhere in the 2GP package, how will we connect to our customer's orgs to sync data (we use the JWT Bearer OAuth flow)? | |
| Jan 28, 2023 at 14:51 | comment | added | Phil W | You do not need to put the Connected App metadata in your package in order to use the connected app on the PBO (which has no namespace and is the DevHub). | |
| Jan 28, 2023 at 14:45 | comment | added | nstuyvesant | Phil W - You mentioned your Connected App was created in your PBO but not in a package. From my understanding, in my 2GP project, the ".connectedApp-meta.xml" file's developerName field should reference the namespace and name of the Connected App. Is your PBO a namespace org? My understanding is that the PBO is normally the org to make the Dev Hub but then it cannot be a namespace org. Curious how your company structured this. | |
| Jan 27, 2023 at 18:01 | comment | added | Phil W | I can't answer that last question; I joined my company after the PBO was in place. Sorry. | |
| Jan 27, 2023 at 17:23 | vote | accept | nstuyvesant | ||
| Jan 27, 2023 at 17:11 | comment | added | nstuyvesant | Based on those links, it looks like we won't have any need for the 1GP. We'll just need the PBO once we are approved as an ISV Partner. Can a PBO trial be converted to a PBO once we are approved? If so, I'll open a ticket with Salesforce. | |
| Jan 27, 2023 at 16:37 | comment | added | Phil W | Take a look at this and this for some more detail. | |
| Jan 27, 2023 at 16:35 | comment | added | Phil W | Do you really need a packaged Connected App? Is it a must that every install gets a different client ID/secret? Or could you use a shared Connected App created on your "Partner Business Org" (PBO; that's the CRM/production org for ISVs)? We took this latter approach. No need to package it, no need for 1GP. | |
| Jan 27, 2023 at 16:30 | comment | added | nstuyvesant | Regarding the naming... no one has the 1GP (only installed once for testing on a Dev org). The only reason it was created in the first place was because Connected Apps have to be created in a 1GP otherwise, I would have started with 2GP and never had this dependency (frustrating). | |
| Jan 27, 2023 at 16:13 | comment | added | Phil W | Naming the 1GP and 2GP packages more-or-less the same is a bit strange. | |
| Jan 27, 2023 at 15:16 | comment | added | nstuyvesant | Thanks Phil. Aurora is the version name but your example is helpful. Let me give this a try. I will also update my question above and post results. | |
| Jan 27, 2023 at 14:58 | history | answered | Phil W | CC BY-SA 4.0 |