Protected Custom Label Can’t be Removed from Package

2gpcustomlabelmanaged-package

I was under the impression that one of the reasons to mark components (such as Custom Labels) as protected is so they can be removed from a Managed Package with little to no fuss as they can't be depended on in unmanaged code. See SF Docs

I tried to remove a Custom Label from our package as it was protected but packaging failed with the error:

Can't create package version. Removing metadata components from a second-generation managed package is a pilot feature that requires acceptance into a pilot program

So I'm guessing it's only a 1GP feature with protected components and in order to delete even protected components you've gotta be in this Beta Program. Seems it's only possible to "Mark Deprecated" for Custom Labels too. Just not sure I see the benefits of using protected labels in 2GP then if their biggest advantage of being able to delete them isn't possible.

Best Answer

As the error says, it's a Pilot feature. That means that salesforce.com will likely open this up for all ISVs in the future, but they want to make sure that there are no bugs that could break package building before opening it up. Keeping the labels protected allows a path forward in the future to delete these components permanently. Unless you need to allow subscriber access to these labels, make sure you keep them protected for now.

Related Solutions

[SalesForce] Custom Settings – Visibility Protected – Managed Package

No. You will not be able to modify the visibility once it is packaged and released

[SalesForce] Lightning components: Custom label translation not working in managed package

My current workaround for this is to add a server side action (custom labels work in apex) that would return a map of all the custom labels used in the component and then set it as an attribute of type "Map". (You need to reference all custom labels anyway in order to include them in a managed package)

bottleneck: You have to make sure you load labels before doing anything else. If you have nested structure of your components and you load labels only once in the root component -> you have to manage loading of custom labels to insure the labels attribute is accessed only when it's populated.

Apex controller:

@AuraEnabled
public static Map<String,String> getCustomLabelMap(){
    Map<String,String> customLabelMap = new Map<String, String>();
    customLabelMap.put('MyCustomLabel1',Label.MyCustomLabel1);
    customLabelMap.put('MyCustomLabel2',Label.MyCustomLabel2);
    return customLabelMap;
}

Lightning Component:

<aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
<aura:attribute name="LABEL" type="Map" access="private"/>

<lightning:button label="{!v.LABEL.MyCustomLabel1}" onclick="{!c.myFunction}" />

Lightning Component Controller:

({
    doInit: function (component, event, helper) {
        var action = component.get("c.getCustomLabelMap");
        action.setCallback(this, function (response) {
                var LABEL = response.getReturnValue();
                component.set("v.LABEL",LABEL);
        });
        $A.enqueueAction(action);
    },
    myFunction: function () {
        //myFunction
    }
})

Best Answer

Related Solutions

[SalesForce] Custom Settings – Visibility Protected – Managed Package

[SalesForce] Lightning components: Custom label translation not working in managed package

Related Topic