Potential regression on #918

[Windyo]

Summary

FSL setting and feature sets result in:

• licenses provisioned
• FSL installed
• FSL not activated and permsets missing

Steps To Reproduce

Create a sratch org using for example

Json

{ "orgName": "Scratch Org", "adminEmail":"[email protected]", "country":"FR", "language":"en_US", "description": "Scratch Org.", "hasSampleData": true, "release": "current", "sourceOrg": "REDACTED", "features": [ "ContactsToMultipleAccounts", "DebugApex", "EnableSetPasswordInApi", "EntityTranslation", "Entitlements", "ForceComPlatform", "Interaction", "FlowSites", "FieldService:5", "FieldServiceDispatcherUser:5", "FieldServiceMobileExtension", "FieldServiceMobileUser:5", "LiveAgent", "MarketingUser", "MultiCurrency", "SalesUser", "SalesforceContentUser", "StateAndCountryPicklist", "RecordTypes", "RefreshOnInvalidSession", "ServiceCloud", "ServiceUser" ], "settings": { "caseSettings": { "closeCaseThroughStatusChange" : true }, "CustomAddressFieldSettings": { "enableCustomAddressField" : true }, "userManagementSettings": { "permsetsInFieldCreation": true, "userAccessPoliciesEnabled" : true }, "currencySettings":{ "enableMultiCurrency": true }, "languageSettings": { "enableTranslationWorkbench": true }, "pathAssistantSettings": { "pathAssistantEnabled": true }, "lightningExperienceSettings": { "enableS1DesktopEnabled": true, "enableUsersAreLightningOnly": true, "enableLexEndUsersNoSwitching": true }, "mobileSettings": { "enableS1EncryptedStoragePref2": false }, "securitySettings": { "enableAdminLoginAsAnyUser": true, "passwordPolicies": { "expiration": "Never", "historyRestriction": "0" }, "sessionSettings": { "sessionTimeout": "TwelveHours" } }, "fieldServiceSettings": { "fieldServiceOrgPref": true }, "chatterSettings": { "enableChatter": true } }, "objectSettings": { "product2": { "sharingModel": "read" }, "account": { "sharingModel": "read" }, "asset": { "sharingModel": "ControlledByParent" }, "contact": { "sharingModel": "ControlledByParent" } } }

Expected result

FSL is installed and activated with default base standard permsets and functions available

Actual result

FSL is installed but inactive

Additional information

Potential regression of #918

System Information

Terminal on Windows

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.89.8",
  "nodeVersion": "node-v22.15.0",
  "osVersion": "Windows_NT 10.0.19045",
  "rootPath": "C:\\Users\\Geoffrey\\AppData\\Local\\sf\\client\\2.89.8-c2dbd99",
  "shell": "cmd.exe",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.28 (core)",
    "@oclif/plugin-commands 4.1.25 (core)",
    "@oclif/plugin-help 6.2.28 (core)",
    "@oclif/plugin-not-found 3.2.51 (core)",
    "@oclif/plugin-plugins 5.4.37 (core)",
    "@oclif/plugin-search 1.2.24 (core)",
    "@oclif/plugin-update 4.6.39 (core)",
    "@oclif/plugin-version 2.2.28 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.39 (core)",
    "@oclif/plugin-which 3.2.35 (core)",
    "@salesforce/cli 2.89.8 (core)",
    "apex 3.6.17 (core)",
    "api 1.3.3 (core)",
    "auth 3.6.120 (core)",
    "code-analyzer 5.1.0 (user)",
    "data 4.0.32 (core)",
    "deploy-retrieve 3.22.10 (core)",
    "info 3.4.60 (core)",
    "limits 3.3.54 (core)",
    "marketplace 1.3.8 (core)",
    "org 5.7.8 (core)",
    "packaging 2.13.3 (core)",
    "schema 3.3.62 (core)",
    "settings 2.4.27 (core)",
    "signups 2.6.26 (user)",
    "sobject 1.4.56 (core)",
    "telemetry 3.6.41 (core)",
    "templates 56.3.47 (core)",
    "trust 3.7.89 (core)",
    "user 3.6.21 (core)",
    "@salesforce/sfdx-scanner 4.12.0 (user)",
    "bbdoc 4.1.0 (user)",
    "sfdmu 4.38.0 (user)",
    "sfdx-git-delta 6.11.0 (user)"
  ]
}

[github-actions[bot]]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[shetzel]

I'm not able to reproduce this with your steps. The CLI team did not do anything to fix #918 . It was fixed by a server side team (signups I believe). The quickest way to a resolution on your issue is to open a support case.

[github-actions[bot]]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.