7.172.0 and Cannot set sharingModel to ControlledByParent
Summary
We get the following error when using 7.172.0 to install an unlocked package into a sandbox. Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field
Steps To Reproduce:
- Just try to install an unlocked package into a sandbox that has any custom child objects with a Master-Detail relationship with the custom parent object and is set to ControlledByParent.
Expected result
Should install successfully, like it does with previous versions.
Actual result
Fails on above error. Stated again, below: Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field
System Information
sfdx-cli/7.172.0 linux-x64 node-v16.17.1
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.
Additional Info - I've started getting this on new org-dependent packages for objects which have not changed in the package. Started post Winter 23 (this weekend)
Version - sfdx-cli/7.173.0 darwin-arm64 node-v16.17.0 Also tested 7.172.0, 7.171.0
Hi @agentgill @dcano421, It sounds like this is related to this weekend's Winter 23 release, I've let some internal packaging teams know so they can look into it. Also as a reminder, try out the pacage:beta:* commands too :)
@WillieRuemmele, thanks William for responding. beta commands seem to be more stable and allowed me to get passed this issue.
Reopening this as some customers have indicated that they cannot use the beta packaging commands in their CI scripts. We'll leave this open until it's been fixed in the force:package:install command in the salesforce-alm plugin.
To be clear, this is working if the force:package:beta:install command is used from the @salesforce/plugin-packaging plugin, but not everyone is comfortable/allowed to use beta commands in their work flows.
This issue has been linked to a new work item: W-12067826