Good afternoon,
Up until recently we have done all of our development inside of our production instance. This means all custom objects and processes have been made in the "Custom" package provided by default.
Now we are trying to move to developing in a separate instance and then exporting at regular intervals to that production instance. The problem is that we don't seem to be able to interact with any of our custom objects once we make a new package and try to start building inside of it. We've tried throwing a bunch of different dependencies at the package to make the custom objects available for use inside of processes and everything else but so far no luck.
Can anyone advise: how do we make use of all of our previous work in Custom inside new custom packages? Is there a particular dependency we might be missing? Does something special have to be done with Custom objects before they're available for reference outside the Custom package?
We've dug through the academy trying to find answers but so far no luck, would appreciate any help you can offer!
Like
Hi Gary,
Have you created a new custom package and moved all the development configurations from the Custom OOTB package to your new package?
Pease brief about the dependencies you have added to your new package.
Best regards,
Bhoobalan Palanivelu.
Can you clarify what you mean by: "Have you created a new custom package and moved all the development configurations from the Custom OOTB package to your new package?"
Does that indicate that in order to utilize anything in the Custom OOTB package thats been developed already we will first need to migrate it over to our new package? (We did not do this)
If we were to do so in Dev, move all of the necessary objects over into the new package, once exported how does that interact with Prod once we import?
Thank you for your help!