Skip to main content
New
Stack Overflow Jobs powered by Indeed: A job site that puts thousands of tech jobs at your fingertips (U.S. only). Search jobs
11 votes
Accepted

Accessing public class from different Package in same Namespace

you forgot to use @namespaceAccessible annotation, in order to make public class accessible across different packages in one namespace. Here is a documentation The @namespaceAccessible annotation ...
Oleksandr Berehovskyi's user avatar
10 votes
Accepted

Custom options added to Standard Value Set picklist are not included into managed package

No, you can't package any standard fields, including standard value sets. Only this list of components is available for packaging.
sfdcfox's user avatar
  • 494k
6 votes
Accepted

Beta Package (Not allowed to install metadata via apex)

Never mind, I found it: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_metadata_in_apex.htm, Specifically: Managed packages not approved by Salesforce ...
jordan.baucke's user avatar
5 votes
Accepted

Detect package type in Apex

I'll start with a quick acknowledgement that you want to do this directly in Apex. I don't think this is currently possible. With the right API call it might be possible to access that information ...
Daniel Ballinger's user avatar
4 votes

How to handle dynamic namespace when packaging lightning components in managed package?

You can get away with the problem of namespace in your lightning components by crafting your own wrapper class structure for your data attributes. The blog post here describes how to create message ...
Mohith Shrivastava's user avatar
4 votes
Accepted

Package Upload Failed(No COMPONENT named markup://Namespace:ligtcomponent found)

I ran into this today, it looks like it is popping up again recently. I can't offer any science but I did get past it. If it's happening to you, try deleting all code in the offending component (...
Daniel Collier's user avatar
3 votes
Accepted

Can any package can be both managed, and installable in production, without requiring appexchange security review?

There are two different things here. Beta Versions of Managed Packages(These can be private manage packages or App exchange managed packages. Private one's doesn't need to go through security review. ...
Hemavantha Rajesh Varma Mudunu's user avatar
3 votes

How to test DX-namespaced package in regular sandbox

There is no magic scripts available to strip of the namespace from the aura components. I usually instruct developers to not use the namespace in code and work towards making components completely ...
Mohith Shrivastava's user avatar
3 votes

How to reinstall a managed beta package without losing custom objects data?

For your point first thats not possible. You need to first uninstall that package first. For second point you can take a offline backup in Eclipse and then remove dependency of your Beta package and ...
Tushar Sharma's user avatar
3 votes
Accepted

Managed package install

What are the repercussions of moving from managed beta to managed release ? The restrictions depend on what you're talking about. For example, objects and fields can't be renamed, fields can't change ...
sfdcfox's user avatar
  • 494k
3 votes
Accepted

How do you convert your beta managed package to final(release) managed package

when you need to publish final managed package you need to check checkbox "Managed - Released" while uploading the package.
Ajay Prakash Dubey's user avatar
3 votes

Downgrade from my latest beta package to previous manage package

You will have to uninstall the BETA package and there is no other alternative here. Things to keep in mind 1.All the new fields you created on the managed objects will have to be deleted to allow ...
Mohith Shrivastava's user avatar
3 votes
Accepted

Can global members be added/removed from Beta packages freely?

Yes, you can switch a never-production-uploaded-global back to its previous access level. You'll only be committed to it if you upload it as a production version. You can also enable "managed package ...
sfdcfox's user avatar
  • 494k
3 votes

Is there a way to promote a managed package from the CLI?

First generation packages can't be promoted. You would use the package1 version create to create a new Released version. You must be using a second generation package in order to use package version ...
sfdcfox's user avatar
  • 494k
2 votes

Cannot undelete package components despite info saying you can

One should be very careful removing components once a Managed Package has been release .The exact behavior you are facing has been documented here To get back the Undelete Action you will need to log ...
Mohith Shrivastava's user avatar
2 votes
Accepted

How to log system.debug messages in Managed package beta version

As sfdcfox has mentioned, this is currently not possible. System.debug information will not be populated in the managed package. However, there are some workarounds in this situation. One solution ...
Lance Shi's user avatar
  • 13k
2 votes
Accepted

Managed installed classes cannot be saved(Tooling API)

It looks like you are trying to use the tooling api to dynamically update a managed package component in the subscribers org. That isn't possible. As you found, components of a manged package can only ...
Daniel Ballinger's user avatar
2 votes
Accepted

design:attribute on Locked Developer Controlled Package upgrade

We figured out the issue. Turns out the aura:attribute referencing the design:attribute needs to have access="global" in order to appear in the Lightning App Builder.
Andrew Turgeon's user avatar
2 votes
Accepted

Metadata that cannot be removed from a beta managed package

I was not aware of the inability to remove flows (1GP beta), so thanks for sharing. However, I believe you are misunderstanding what this means. I believe this is simply saying that flows from 1GP or ...
Phil W's user avatar
  • 36.7k
2 votes

Getting error when creating 2gp package version

Manageability rules do not allow you to delete components from your managed package at will. While second-generation packaging allows a broad scope of components to be deleted, you must first log a ...
David Reed's user avatar
  • 93.1k
2 votes

Error (1): The requested resource does not exist Faced, While creating 2nd generation Managed Package

I just found the solution on my own. There was a permission in dev hub org Enable Unlocked Packages and Second-Generation Managed Packages which was not enabled. I just enabled it and now everything ...
Parvez Alam's user avatar
2 votes

Managed Package Upgrade Strategy for Beta Versions or Promote Version

Beta versions exist to allow you to make experimental changes in your managed package. These changes get "baked in" to the package, in an irreversible way**, when you include them in a ...
Phil W's user avatar
  • 36.7k
1 vote

How to optimize Managed Beta Package Testing process?

You shouldn't need to use a cycle like this with modern development practices. Create a Scratch Org, linked to your package's namespace, deploy your code there, do any development you want to do (...
sfdcfox's user avatar
  • 494k
1 vote
Accepted

Creating a Second Generation Managed Package with configuration link

As of now, we don't have the possibility to show a configuration Link on Second Generation Managed Package(2GP) as in First Generation Managed Package(1GP). This is one of the drawbacks of 1GP to 2GP.
Deep's user avatar
  • 33
1 vote
Accepted

Upload beta package - how to bypass or speed up tests execution

So I'm wondering if there is a way to bypass/suppress tests execution when uploading beta package. No, 1GP (First Generation Packaging) always requires tests. This applies even to unmanaged packages....
sfdcfox's user avatar
  • 494k
1 vote

Package upload fail : No Component named markup found?

We've been seeing this issue as well. Salesforce has told us there is an issue that is affecting many partners/ISV and a KI is in the works. Which doesnt solve our problem as we cannot create a ...
RockPile's user avatar
  • 303
1 vote

Package Upload Failed(No COMPONENT named markup://Namespace:ligtcomponent found)

In your packaging org, you use the default namespace c. This makes it easier to migrate code between your packaging org and any developer orgs you may be using.
sfdcfox's user avatar
  • 494k
1 vote

Custom options added to Standard Value Set picklist are not included into managed package

Standard value sets are still not supported at the time of MD API version 45. Latest support metrics for what can be and can't be packaged is here: https://developer.salesforce.com/docs/metadata-...
Tuto's user avatar
  • 133
1 vote

New picklist value not being added to upgraded package

I just ran into the same issue. A new picklist value was added to a field and then deployed via a non-beta managed package update. After the new package was installed the picklist value wasn't ...
Daniel Ballinger's user avatar
1 vote

New picklist value not being added to upgraded package

Reading an other post in stackexchange, it seems that the new picklist values are not added when the package is upgraded, so my recommendation is why not to try adding the field value in a post ...
D. Cruz's user avatar
  • 534

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