Promoting Changes on Custom Objects

[mandypayne]

Describe the bug We ran into some issues when promoting changes to custom objects where only the object metadata file was changed - profile search layout changes and name field changes. The changes are reflected in GitHub and the promotion appears to complete successfully, but the object changes are not actually deployed.

To Reproduce Steps to reproduce the behavior:

1. Create a work item in DevOps Center
2. In a development environment, change the Name field type a custom object from text to auto-number
3. Add the object change to the work item and commit
4. Query the Submit Components related to the work item:

   SELECT sf_devops__Change_Submission__c, sf_devops__Empty__c, sf_devops__File_Path__c, sf_devops__Operation__c, sf_devops__Source_Component__c, sf_devops__Source_Remote_Change__c 
   FROM sf_devops__Submit_Component__c 
   WHERE sf_devops__Change_Submission__r.sf_devops__Work_Item__r.Name = '{work item name}' 

5. The sf_devops__File_Path__c points to a file that is not the custom object's metadata file
6. When promoting the work item, the custom object's Name field type is not updated in the target environment

Expected behavior

1. The sf_devops__File_Path__c references the custom object's metadata file
2. Promoting the work item causes the custom object to be updated based on the changes that were made

Screenshots Incorrect file path on Submit Component:

Corrected file path:

Additional context We are able to work around this by manually updating the File Path on the Submit Component that references the custom object. We first have to inactivate the validation rule that prevents this change, and then activate again when we are done making the change.