function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Jonathan 2Jonathan 2 

Package automatically converted to an extension.

This particular developer account contains a package which I have been working for a while. All the classes and objects are contained within this account and it has been certified.

 

Last week another app was deployed in this developer account for demo purposes. Today I have noticed that the main package (the one we are developing) in this account has actually become an extension of this demo application.

 

Not sure why and how this has happened since the two name spaces are different. Any ideas on how I should go about fixing this?

 

Thanks in advance.

Best Answer chosen by Admin (Salesforce Developers) 
A_SmithA_Smith

Sounds like something in your main package is referencing something in the installed package.  When you view the list of components in your main package, you should see in the far right column a note that tells you what component form the second package is being pulled into the main.  That same row should also tell you want component in the base is referring to the second package.  You simply need to stop your main package component from referring to that second package component.

 

Thanks, 

All Answers

A_SmithA_Smith
So both of these packages were installed in your dev org?  Or did you create the main package in the org?
Jonathan 2Jonathan 2

Thanks Andrew

 

The main package was actually created in this account. The second package was installed at a later stage.

 

Cheers
A_SmithA_Smith

Sounds like something in your main package is referencing something in the installed package.  When you view the list of components in your main package, you should see in the far right column a note that tells you what component form the second package is being pulled into the main.  That same row should also tell you want component in the base is referring to the second package.  You simply need to stop your main package component from referring to that second package component.

 

Thanks, 

This was selected as the best answer
Jonathan 2Jonathan 2

Thanks Andrew

 

That was it. A dashboard referencing a report referencing an object from the second package.

 

Easy fix in the end.

 

Cheers