Apex Code Development You need to sign in to do that
Don't have an account?
Sanju Rana 5 Question on packaging and then creating dependent package
Hi All,
I am looking for the advise for my below scenario.
We are into a very initial stage of our development and we have a requirement where we need to create two different packages (from two different development orgs), those two packages will use some objects which are common to both packages. So what I thought was.
1) Create a package with the common objects.
2) Install common objects package in development org1 and create dependency on "common objects package".
3) Install common objects package in development org2 and create dependency on "common objects package".
By doing this I do not have to duplicate the objects but I am concerned that once I create a package with the common objects and if while doing development in development org1 or in development org2 I realized that I need to change the data model of "common objects" then I'll not be able to do this easily (becase common objects is already released as a managed package).
Is their any better solution available to such problem? Please advise.
Thanks!
I am looking for the advise for my below scenario.
We are into a very initial stage of our development and we have a requirement where we need to create two different packages (from two different development orgs), those two packages will use some objects which are common to both packages. So what I thought was.
1) Create a package with the common objects.
2) Install common objects package in development org1 and create dependency on "common objects package".
3) Install common objects package in development org2 and create dependency on "common objects package".
By doing this I do not have to duplicate the objects but I am concerned that once I create a package with the common objects and if while doing development in development org1 or in development org2 I realized that I need to change the data model of "common objects" then I'll not be able to do this easily (becase common objects is already released as a managed package).
Is their any better solution available to such problem? Please advise.
Thanks!
You can always create the extension package based on the already deployed "Common Objects" package and deploy the same in your different organizations