[SalesForce] Unlocked Package Dependency Missing Organization Feature Knowledge

Error when creating new version of unlocked package.

An error occurred while trying to install a package dependency,ID 04XXX: Missing Organization Feature: Knowledge

sfdx-project-json

        "path": "force-app",
        "default": true,
        "package": "memberone",
        "versionName": "July 22 2019",
        "versionNumber": "0.2.11.NEXT",
        "definitionFile": "config/project-scratch-def.json",
        "dependencies": [...

config/project-scratch-def.json

    {
"orgName": "MemberOne",
"edition": "Enterprise",
"features": ["Communities", "Sites", "Knowledge"],
"settings" : {
    "orgPreferenceSettings": {
        "chatterEnabled": true,
        "s1DesktopEnabled": true,
        "networksEnabled": true,
        "knowledgeEnabled": true
},
    "knowledgeSettings":{
        "enableKnowledge": true,
        "enableLightningKnowledge": true,
        "
    }
}

}

When I use the scratch-def to create scratch org directly it seems to work fine and dependent package 04XX installs.

Best Answer

The force:package:version:create command takes a definition file as an optional argument, where you can specify the required dependencies:

-f | --definitionfile DEFINITIONFILE
Optional
The path to a definition file similar to scratch org definition file that
contains the list of features and org preferences that the metadata of the
package version depends on.

Despite the phrasing "similar to", as far as I know it's exactly the same as your project's standard scratch org configuration file, as illustrated in Generate a Package Version.

That sets the shape of the under-the-hood scratch org used to build the package version.

I'll answer as I did find some kind of workaround

Those steps allow me to work DX-style with Managed Package, Namespace and Person Account

1 Create scratch org WITHOUT Namespace, using flag -n, --nonamespace

sfdx force:org:create -f config/project-scratch-def.json -a ScratchNONameSpace -s -n

2 First thing is to pull Account.Business_Account, which works as expected

$ sfdx force:source:status -r

=== Source Status
STATE       FULL NAME                 TYPE        PROJECT PATH
Remote Add  Account.Business_Account  RecordType

$ sfdx force:source:pull

=== Pulled SourceSTATE  FULL NAME                 TYPE        PROJECT PATH
Add    Account.Business_Account  RecordType  force-app/main/default/objects/Account/recordTypes/Business_Account.recordType-meta.xml

3 Create scratch org WITH Namespace

sfdx force:org:create -f config/project-scratch-def.json -a ScratchWithNameSpace -s

4 Check status, you'll see conflicts

$ sfdx force:source:status
=== Source Status
STATE                      FULL NAME                 TYPE        PROJECT PATH

Local Add (Conflict)       Account.Business_Account  RecordType  force-app/main/default/objects/Account/recordTypes/Business_Account.recordType-meta.xml
Remote Changed (Conflict)  Account.Business_Account  RecordType  force-app/main/default/objects/Account/recordTypes/Business_Account.recordType-meta.xml

5 Push your code using flag -f, --forceoverwrite

$ sfdx force:source:push -f
=== Pushed Source
STATE  FULL NAME                 TYPE        PROJECT PATH

Add    Account.Business_Account  RecordType  force-app/main/default/objects/Account/recordTypes/Business_Account.recordType-meta.xml

$ sfdx force:source:status
=== Source Status
No results found

After that you would be able to push/pull without issues.

[SalesForce] Unlocked Package Dependencies

From the documentation you will need to specify dependency using dependencies property in the project-sfdx.json.

{
  "packageDirectories": [
    {
        "path": "atlas-quantum",
        "default": true,
        "package": "atlas-quantum",
        "versionName": "ver 0.1",
        "versionNumber": "0.1.0.NEXT",
        "dependencies": [
            {
               "package": "fflib-apex-mocks@0.1.0.1"

            },
            {
               "package" : "fflib-apex-common@0.1.0.1"
            }
        ]
    }
],
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "46.0",
"packageAliases": {
    "fflib-apex-mocks@0.1.0.1": "04t1K000002uwEIQAY",
    "fflib-apex-common@0.1.0.1": "04t1K000002uwENQAY",
    "atlas-quantum": "0Ho1K000000k9cQSAQ",
    "atlas-quantum@0.1.0-1": "04t1K000002uwCRQAY",
    "atlas-quantum@0.1.0-2": "04t1K000002uwCWQAY"
   }
}

Best Answer

Related Solutions

[SalesForce] SFDX PersonAccount: ERROR: Entity of type ‘RecordType’ named ‘Account.Business_Account’ cannot be found

I'll answer as I did find some kind of workaround

Those steps allow me to work DX-style with Managed Package, Namespace and Person Account

[SalesForce] Unlocked Package Dependencies

Related Topic