10

Although this post is from last year, I would like to address it since it's apparently coming up in search results for those looking to post unmanaged packages to the AppExchange, and the main answer currently features out-of-date info. To confirm, unmanaged packages are not accepted for security review or posting on the AppExchange. I've put together some ...


9

Having unmanaged package installation approach in production you can't Uninstall the package if it is being referenced by component which is not part of that package You can not upgrade unmanaged packages. You will have to uninstall the previous one. You cannot overwrite a component which has same API name in production but not part of the package and ...


8

Update Salesforce does not allow unmanaged packages to be part of appexchange .You will have to convert them to managed packages . You can publish your apps as managed package to the appexchange provided you sign up as partner.Do not confuse that partner has to be some consulting firm .Anyone can be a partner Even as a solo developer you can be a part of ...


7

It's not possible with that method. The InstalledPackage metadata type requires a namespace and unmanaged packages don't have one. What you can do is install the unmanaged package into an org and then do a retrieve of the package's metadata. You can use the retrieved package metadata to deploy into any other org via ant or any other deployment tool. It ...


7

I was able to replicate this issue in two packages, so have raised it with support, and they are currently researching it (they were able to re-create it) One thing I noticed as a workaround - I had many classes with mock callouts, both Web Service and HTTP. But only some failed - and they both did NOT make use of Start/Stop Test. So even though they ...


7

You can remove metadata from being part of the Unlocked Package in the UI. In the org where the Unlocked Package was installed, go to Setup/Installed Packages, click on your package name and then on the "View Components" button. You'll have a "Remove" button next to your elements. This won't delete anything, just "unflag" your metadata from being part of ...


6

Yes. You are able to edit all of the components that are part of an unmanaged package. From the Overview of Packages page. Unmanaged packages Unmanaged packages are typically used to distribute open-source projects or application templates to provide developers with the basic building blocks for an application. Once the components are installed from ...


5

Create a free Developer Account Then you can create a namespace and a managed package. Link to info on managed packages: https://help.salesforce.com/apex/HTViewHelpDoc?id=enabling_managed_packages.htm&language=en Use an IDE to migrate the metadata for your objects / field / code to the new DE account Talk to your AE to see what they can do with your ...


5

The package components would need to be moved to a different org (easy to do if they are already under version control as they should be) and a new unmanaged package definition created there. But note that the unmanaged package components would not have a namespace so it would be hard to change an existing installation that used the managed package into one ...


5

Generally, is it possible to install two unlocked packages that share overlapping Metadata, e.g. the same custom object? One would need to be a dependent of the other if the exact same metadata exists. Note, however, that a custom object has many related components, which of which may be unique. For example, you might have a custom object, and a dependent ...


4

Well it is not possible to go from managed to unmanaged package.You need to copy all your code to a new org without a suffix.


4

Once you get the unmanaged package link ,you will replace login with test Lets say your unmanaged package link is https://login.salesforce.com/packaging/installPackage.apexp?p0=04t28000000B4ng Your package link for sandbox is as below https://test.salesforce.com/packaging/installPackage.apexp?p0=04t28000000B4ng Edit Also note it takes significant ...


4

View Installed Package Details To access the package detail page, from Setup, enter Installed Packages in the Quick Find box, select Installed Packages, and then click the name of the package that you want to view. It's right under the Build section, not even nested. Here's what the page looks like: Installed Packages Help for this Page On ...


4

This question is, effectively, asking the difference between authorization and authentication. OAuth 2.0 is an authorization standard. The access token you receive from the server authorizes you to make requests against the server (in this case, the Salesforce API) and access specific resources without having to store the user's credentials. You declare ...


4

The only way to call dynamic methods is to use instance logic. So you'll need an interface layer here: public interface StaticMethod { void execute(); } Then your implementations would look something like: public class MyManagedMethod implements StaticMethod { public void execute() { MyManagedClass.doStuff(); } } Then you can ...


4

Post Install only works for the managed packages and do not run for the unmanaged packages .Check the official docs here .


4

Managed packages, so far as I know (trying to migrate my company to SFDX myself as well) are not carried over to scratch orgs. I'm not familiar with the error that you're seeing, but if you happen to try to push code, fields, validation, etc... that make use of managed packages, sfdx has complained to me about "not able to deploy components in a different ...


4

So i found out what the problem is Connected Apps are not available in Unmanaged Packages, they are available in managed Packages.


3

If your end goal is to create an unmanaged package you shoud be able to do that right in the developer org. For a nice walkthrough go here, it walks you through creating a simple class and packing it up in a Developer org. To get going, log in to your Developer Environment and then go to Setup -> Develop -> Apex Classes to create the class. Now you'...


3

Three suggestions I can think of. First, change your unit test class to at least version 28.0, and make sure you are using @isTest or @isTest(SeeAllData=false). This should give you isolation from production data, and probably allow your tests to pass. Second, your query is non-selective because you are using both a NOT EQUALS operator, and a non-indexed ...


3

Creating a managed package is just as easy as creating an unmanaged package. The only requirement to create a managed package is that you’re using a Developer Edition organization. You can follow below steps. signup for a new developer organzation. Create unmanaged package from your current org. Install that package in your developer organization created ...


3

Development tools such as the Force.com IDE (and others - see this Force.com Tools and Toolkits list) allow configuration and code from one org to be extracted to your local PC and then pushed from there into a different org. If you don't need the IDE facilities, the Force.com Migration Tool - Ant tasks - can be used instead as they are only concerned with ...


3

I don't think that deleting packages will remove the components associated with it. Here is something you can read from Salesforce From the list of packages, you can: Click New to create a new package, enter a package name and description, and Click Save to store it in your list of packages. Click Edit to update the package properties. ...


3

It seems to be namespace issue: Try replacing to below syntax: <span id="gaconnector_pages_visited_list"><apex:outputField value="{!lead.Pages_visited__c}" /> </span>


2

No packaged code is scanned, whether managed or unmanaged. There is a legitimate use case to scan unmanaged packages, but there is a workaround to deploying the code into a DE org directly, so this is not a high priority at the moment. We cannot scan managed packages because there are IP protections in place that prevent disclosure of source code, ...


2

We've been working on NPSP 3.0 for the last 9 months and are getting very close to a release. The new version is currently under security review as part of the standard process for listing on the AppExchange. I'm not sure if the security scan results are allowed to be published but will check to see if that's possible and/or advisable. We're an open ...


2

It means that if your application uses a managed package then that managed package will not be scanned The scanner will only scan the namespace of the org that the scan is being run on. So if you are installing the Starter Pack into your org, it will not be scanned. Also, in order for a package (Managed) to be approved, it basically meets the criteria of ...


2

This is a really subtle shortcoming of Permission Sets and Profiles. Go and vote on the idea now! If you truly need to automate this, it's not impossible. You could stage up a page with the correct checkboxes selected with some URL hacking and send that back to the user like the following example: InstallAppController.cls (use API 31.0 or app returns 0DS ...


2

It depends on the package. If the package contains hard references to its managed package namespace or any code which can only be deployed into a managed packaging org such as @deprecated, you will be unable to install it into anything but the packaging org. Another thing that can block deploying as unmanaged code is if the package.xml contains the ...


2

You cannot have more than one managed package for the same namespace The developer settings in a Developer Edition organization allow you to create a single managed package, upload that package to the AppExchange, allowing other users to install and upgrade the package in their organization. After configuring your developer settings the first time,...


Only top voted, non community-wiki answers of a minimum length are eligible