I wonder if there is a feature or setting to mention on scratch org definition file, so that Permission Set License "FinancialServicesCloudExtension" be assigned to the scratch org user?
I see it works in case of "ActionPlans" PS is auto-assigned to the "User User", if there is the feature "IndustriesActionPlan" mentioned on the scratch org definition.
"FinancialServicesCloudExtension" PS is required for the deployment user to get access to Branch Management objects (BranchUnit, BUBM, etc.) Otherwise, the related metadata cannot be packaged. #Financial Services Cloud #Scratch Org Definition #Scratch Org Configuration #Unlocked Packages
I also tried to use "IndustriesBranchManagement" feature on the scratch org defintion. The scratch org has been created with PS "Financial Services Cloud Comprehensive", but the PS is not assigned to the user. Package:version:create is still failing, as the user doesn't have access to Banker standard fields (my understanding).
The user has access to the fields, once either PS "Financial Services Cloud Comprehensive" or "Financial Services Cloud Extension" assigned to the user.
@Emily Kapner, I wonder how this KI (Unlocked package creation with dependency on Financial Services Cloud object BranchUnitBusinessMember) was resolved back in Winter '22 ? Ability to package Branch Management related metadata would be huge progress (with all the Apex Classes, Triggers and Flows created based on it).
