---
schema_version: "1"
id: 47b85fc5e91fc2ba9866c7d648b2a2a693f1a7310edda7ded032cc66841acd5e
title: Submit Component (sf_devops__Submit_Component__c)
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/salesforcedx/devops-center-dev/guides/devops-center/custom-objects/sforce-api-objects-sf-devops__submit-component__c.md
canonical_url: https://developer.salesforce.com/docs/platform/devops-center-dev/guide/sforce-api-objects-sf-devops__submit-component__c.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 2ff59cfd90a33710e0daebfead3a875295aa9a7eb41760ee61c0fb324fa3e681
products:
  - DevOps Center Developer Guide
  - salesforcedx
---

# Submit Component (sf_devops__Submit_Component__c)

Represents a metadata component that was committed to a feature branch in the source control repository. The commit can be initiated in one of two ways, either from within DevOps Center or directly in the source control repository. Each metadata component that’s part of the commit must also be deployed to an environment, and DevOps Center uses the Submit Component object to model the metadata. The Submit Component object is a child of Change Submission. This object is available in all orgs that have DevOps Center installed.

## Supported Calls

`create()`, `delete()`, `describeLayout()`, `describeSObjects()`, `getDeleted()`, `getUpdated()`, `query()`, `retrieve()`, `undelete()`, `update()`, `upsert()`

## Fields

|Field|Type|Properties|Description|
|-----|----|----------|-----------|
|`Name`|string|Autonumber, Defaulted on create, Filter, idLookup, Sort|Name of this Submit Component record.|
|`sf_devops__Change_Submission__c`|reference|Create, Filter, Group, Sort|Reference to the parent Change Submission record that this Submit Component record is a child of. This field is a relationship field. Relationship name: sf_devops__Change_Submission__r. Relationship type: Master-detail. Refers to: sf_devops__Change_Submission__c.|
|`sf_devops__Empty__c`|boolean|Create, Defaulted on create, Filter, Group, Sort, Update|If `true`, indicates that the metadata component didn’t change anything on the associated feature branch. This scenario occurs when a user pulls removed metadata from a development environment, but the metadata source doesn’t yet exist on the feature branch. DevOps Center still removes the metadata from the environment but doesn’t change the feature branch. The default value is `false`.|
|`sf_devops__File_Path__c`|string|Create, Filter, Group, Nillable, Sort, Update|Full pathname of the `-meta.xml` source file for this component on the feature branch.|
|`sf_devops__Operation__c`|string|Create, Filter, Group, Sort, Update|Specifies the operation that was executed on this component. Either `ADD`, `CHANGE`, or `DELETE`.|
|`sf_devops__Source_Component__c`|string|Create, Filter, Group, Sort, Update|Combination of the metadata name and type.|
|`sf_devops__Source_Remote_Change__c`|reference|Create, Filter, Group, Nillable, Sort, Update|If a user in DevOps Center initiated the commit, this field is a reference to the associated Remote Change record that displayed the component in the user interface. This field is a relationship field. Relationship name: sf_devops__Source_Remote_Change__r. Relationship type: Lookup. Refers to: sf_devops__Remote_Change__c.|

**See Also**  


-   [Change Submission (sf_devops__Change_Submission__c)](https://developer.salesforce.com/docs/platform/devops-center-dev/guide/sforce-api-objects-sf-devops__change-submission__c.md)
-   [Remote Change (sf_devops__Remote_Change__c)](https://developer.salesforce.com/docs/platform/devops-center-dev/guide/sforce-api-objects-sf-devops__remote-change__c.md)

