#Unlocked Packages0 utenti parlano di questo argomento

Hi Community,

I am learning on Salesforce Unlocked Packages for developing an Internal application.

While going through the module  Unlocked Packages for Customers, I noticed that after a package version is created, anyone can install this unlocked package by using the Package Version Id.

The only protection mechanism available is only the installation key.

Since Unlocked Packages is being advocated for distributing internal applications on Salesforce, are there any additional measures that provide a more secure means of protecting the distribution of Unlocked Packages for internal usage?

Appreciate any advice on this.

Thank you!

Regards,

Win

#Appexchage Apps  #Unlocked Packages

#Security

#Package Installation

Does anyone know an easy way to identify the org settings and features required for package components? And does anyone have general advice for troubleshooting package version create errors?

I've been trying to create an unlocked package with components that require custom campaign influence, and it took a long time for me to figure out that I needed to add the appropriate setting in my definition file (scratch org config file): "campaignSettings: {"enableCampaignInfluence2": true}.

I was able to create the first package version successfully, but now I'm getting errors on the version create again. The only thing I changed was adding reports and dashboards based on the CustomizableCampaignInfluence report type, which is a standard report type that gets generated when the custom campaign influence is enabled.

"ERROR running force:package:version:create: MultiTouchCampaignAttribution/Campaigns_Responses_Timeline_32e: ReportType: CustomizableCampaignInfluence is not available,MultiTouchCampaignAttribution/Revenue_by_Opportunity_Type_nhZ: ReportType: CustomizableCampaignInfluence is not available,MultiTouchAttributionDashboards/caDFoKVGnLTwriPidsJZVCMKlDyojs: In field: report - no Report named MultiTouchCampaignAttributionReports/Campaigns_Responses_Timeline_32e found,MultiTouchCampaignAttribution/Top_Campaigns_SB1: ReportType: CustomizableCampaignInfluence is not available"

Is there another org setting or feature I need to add to the definition file? I can't add this report type to the package because it's standard. I tried adding a custom report type that uses the campaign influence object instead, but that didn't work either.

I noticed that when I create a new scratch org with that config file, I can't access campaign influence records until I assign my user the Sales Cloud User or CRM user permision set. I tried including this in that config file,

"features": ["SalesUser"] 

but that just adds the Sales Cloud User permission set to the org, not assign it to my user. Maybe the package version create fails because no user in the scratch org can access the campaign influence object until that permission set is assigned. Do I need to create a script or something to automate the permission set assignment during the scratch org creation process?

Hi guys! I'm looking for someone with experience using the --upgrade-type flag who can clarify the meaning of the different options.

I've found documentation in two different places that says different things.

In the Salesforce CLI Command Reference:

• DeprecateOnly: Mark all removed components as deprecated.
• Mixed: Delete removed components, except for custom objects and custom fields, that don't have dependencies.
• Delete: Delete all removed components that can be safely deleted, and deprecate the other components.

In the Salesforce DX Developer Guide:

• Delete: specifies to delete all removed components, except for custom objects and custom fields, that don’t have dependencies.
• DeprecateOnly: specifies that all removed components must be marked deprecated. The removed metadata exists in the target org after package upgrade, but is shown in the UI as deprecated from the package. This option is useful when migrating metadata from one package to another.
• Mixed (the default): specifies that some removed components are deleted, and other components are marked deprecated. For more information on hard-deleted components, see Hard-Deleted Components in Unlocked Packages.

Mixed in the first and delete in the second have the same text. I understand that the mixed option works as described in the Salesforce DX Developer Guide taking into account the list of Hard-Deleted Components in Unlocked Packages, but I don't understand what the difference is with the delete option. What other metadata does this option delete that mixed doesn't?

#Unlocked Packages  #Metadata

Hi guys! We wanted to include some custom fields and record types to Knowledge object (Knowledge__kav) to our namespaced unlocked package with intention to have the same functionality in 1GP managed package. Creating a version was ok, but when we tried to install it, the errors were thrown.

In case we included in the package only fields and record types folders under objects/Knowledge__kav folder, the following errors showed:

1. (Learning__c.Knowledge__c) referenceTo value of 'Knowledge__kav' does not resolve to a valid sObject type

Learning__c.Knowledge__c: referenceTo value of 'Knowledge__kav' does not resolve to a valid sObject type

2. (Knowledge__kav.Type__c) Entity not available

The Entity 'Knowledge__kav' is not found. Contact the vendor for more details.

3. (Knowledge__kav.Audio_recording) Unable to find the SObject type for the record type 'Knowledge__kav.Audio_recording'

Knowledge__kav.Audio_recording: Unable to find the SObject type for the record type 'Knowledge__kav.Audio_recording'

4. (Knowledge__kav-Audio_recording) Parent entity failed to deploy

Knowledge__kav-Audio_recording: Parent entity failed to deploy

5. (Knowledge__kav) In field: fullName - no CustomObject named {namespace}__Knowledge__kav found

Knowledge__kav: In field: fullName - no CustomObject named {namespace}__Knowledge__kav found

6. (Knowledge__kav-en_US) Invalid object name: Knowledge__kav

Knowledge__kav-en_US: Invalid object name: Knowledge__kav

If we tried to include Knowledge__kav.object file inside objects/Knowledge__kav folder, another error was added at the beginning:

1. (Knowledge__kav) When Lightning Knowledge is enabled, you can’t add an article type.

Knowledge__kav: When Lightning Knowledge is enabled, you can’t add an article type.

Seems it treats that knowledge object as namespaced that comes from the package

It would be very useful if anyone can give a hint how to resolve this. Or only solution is to have no namespaced unlocked package?

Thanks!