I have a requirement to convert a Master Detail to a Lookup field. This has been successfully completed but when trying to deploy this change to the target environment it is stating that on a related list to the lookup object that the customobject.NAME is an invalid field. The field is definitely there is it's the standard ID field (label) and API Name is (Name). I am wondering if anyone else has encountered this and knows of a possible fix? Is the metadata still trying to look for a field with Name but type is Master-Detail? Even when looking in the metadata I see that the standard Name field for any object is actually not present. Thanks!
Add a comment
|
2 Answers
From what I remember it's a common issue with Metadata API.
Verify that you have the related field in the deployment package and that you have object.xml files for both objects, some of the changes can fail you don't have those.
If it still fails then perform it as manual steps. This kind of changes are usual quite temperamental
This is a common validation error as ytiq mentioned. If I am reading this correctly that you can't seem to find the standard field in the target org when looking. Then its possible your deployment user doesn't have access to that standard field, which is common if its not enabled for your profile.
This would result in the Metadata API (assuming thats what your using) can't read this field from the access your deployment account has. I recommend checking in the target that the profile you are using does indeed have access to this field.
Hope this helps.
