We have had a managed package for a couple of years that works alongside an external app which does remote depoyments using the Metadata API. Specifically the external app creates custom fields in 2 custom objects of the package.
These two custom objects are in a Master-Details relationship, and the OWD are Public Read/Write for the master one, and Controlled By Parent on the detail/child one.
The remote deplyments via the Metadata API use the File deployment, and in the XML for the detail/child object we always included the XML: <sharingModel>ControlledByParent</sharingModel>
In the last couple of weeks this has been causing the remote deployments via the Metadata API to fail with the following message: Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field
It looks that something has changed in the way the Metadata API works. Could somebody shed some light into it ?
We have had a managed package for a couple of years that works alongside an external app which does remote depoyments using the Metadata API. Specifically the external app creates custom fields in 2 custom objects of the package.
These two custom objects are in a Master-Details relationship, and the OWD are Public Read/Write for the master one, and Controlled By Parent on the detail/child one.
The remote deplyments via the Metadata API use the File deployment, and in the XML for the detail/child object we always included the XML: <sharingModel>ControlledByParent</sharingModel>
In the last couple of weeks this has been causing the remote deployments via the Metadata API to fail with the following message: Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field
It looks that something has changed in the way the Metadata API works. Could somebody shed some light into it ?
