-
Notifications
You must be signed in to change notification settings - Fork 254
Open
Labels
Description
Describe the issue
Set-BcContainerFeatureKeys is not enabling feature keys because it tries to update record in Tenant Feature Key
table but record is missing initially and only created when you enable feature manually via UI.
Scripts used to create container and cause the issue
Option one. Using featureKeys
parameter
New-BcContainer -accept_eula -artifactUrl (Get-BCArtifactUrl -type OnPrem -country w1 -version 24.3) -memoryLimit 16G -includeAL -containerName KZW1 -auth Windows -includeTestToolkit -includeTestLibrariesOnly -shortcuts None `
-featureKeys @{"ExtensibleExchangeRateAdjustment" = "All Users"; "ExtensibleInvoicePostingEngine" = "All Users"}
Option two. Using Set-BcContainerFeatureKeys
cmdlet
New-BcContainer -accept_eula -artifactUrl (Get-BCArtifactUrl -type OnPrem -country w1 -version 24.3) -memoryLimit 16G -includeAL -containerName KZW1 -auth Windows -includeTestToolkit -includeTestLibrariesOnly -shortcuts None
Set-BcContainerFeatureKeys -containerName KZW1 -featureKeys @{"ExtensibleInvoicePostingEngine"="1"}
Full output of scripts
Setting feature keys on database: CRONUS
Setting feature key ExtensibleInvoicePostingEngine to 1 - Failure
WARNING: Unable to set feature key ExtensibleInvoicePostingEngine
Here is the Feature Management
list. Feature (1) I've just enabled, feature (2) is not enabled but present in the list.
Here is the content of Tenant Feature Key
table in the database. Feature (1) is present and enabled. Feature (2) is not present.
Additional context
BCContainerHelper version 6.0.19