Skip to main content

#DevOps Center8 discussing

When deploying PersonAccount rules, this is the error received. 

Account.Person_Account_Warning_LN_Address of Type failed to deploy due to An object 'Account.Person_Account_Warning_LN_Address' of type DuplicateRule was named in package.xml, but was not found in zipped directory  

 

Has anyone found a solution to fix this? 

 

#DevOps Center  #Deployment

2 answers
  1. Oct 27, 10:57 AM

    Hi @Harsha Shashikanth

    This error may occur when the DuplicateRule is referenced in package.xml but its corresponding metadata file is missing from the deployment package.

    I would recommend trying the following steps:

    1. Verify that Person_Account_Warning_LN_Address exists in the source org under Setup → Duplicate Rules.
    2. Retrieve the duplicate rule again from the source org and confirm that its metadata file is present in the project.
    3. Check that the duplicate rule is correctly referenced in package.xml and that its API name matches the metadata file.
    4. Review your .forceignore file to ensure that the duplicateRules directory or its metadata files are not being excluded.
    5. Refresh or synchronize the DevOps Center work item with the source branch and verify that the duplicate rule is included in the deployment package.
    6. If the issue persists, try retrieving and deploying the duplicate rule separately using Salesforce CLI to determine whether the problem is specific to DevOps Center.

    Also, check whether the target org has Person Accounts enabled and whether the required matching rules and duplicate rules are available.

    Official references:

    I hope this helps! If you find this answer helpful, please select it as the Best Answer. 

     

    Thank, 

    Deepak Sachdeva 

    Nubys Technology Pvt. Ltd.

0/9000

I'm working in Lifecycle Center. 

 

I deleted an inactive process builder and want to add it to a work item so I can commit, review, etc and push it through the pipeline. 

 

The deleted item does not appear in the metadata, hence I'm unable to add it to the work item. 

 

How do I fix this? 

 

#DevOps Center

3 answers
  1. Oct 14, 9:08 PM

    @Deepak Sharma I did some additional research and it seems that SF does not support the deployment of deleted process builders and it must be done manually in every org. If you think this is incorrect, I would appreciate your perspective.

0/9000

I read the documentation which clearly states that once you publish a work item to a pre-production environment, such as UAT, you can't change it. 

 

How does that work? 

 

Work Item is in UAT, and it has to be changed before moving to production. This work item that is either wrong or incomplete.  

 

What is the path to update a work item so it is ready for production? 

 

#DevOps Center

2 answers
0/9000

Can we customise the work item status like New, in progress etc can we customise the work item according to our need?

 

 

#DevOps Center

1 comment
  1. Oct 14, 5:38 PM

    Based on my research, Work Item Status Values cannot be customized because they drive automation. I haven't tried this, but Work Item is an object so you should be able to create a new custom field. You'll have to do some research for ways to expose it with Lifecycle Center so your users can access it.

0/9000

I migrated from Managed Package DevOps Center to Next Generation Dev Ops Center. Now I am not able to activate pipeline or re-authenticate the Source Control Repository. The branch associated with UAT and Prod seems to be OK, because when I click on the branch it opens OK in GitHub. I am having difficulty is selecting a branch for Integration stage.  

 

 

Having difficulty with activating Pipeline in Next Generation DevOps Center

 

Have anyone got any tips for me to follow, thank you so much. 

 

#DevOps Center

2 answers
0/9000

 Hello Trailblazers, 

 

I’m encountering an issue when trying to add a development environment in the Salesforce DevOps Center. After entering my login credentials, I receive the following error message:

 

 "We can't log you in because of an authentication error. For help, contact your Salesforce administrator." 

 

 Has anyone experienced this issue or have additional suggestions for troubleshooting? Any help would be greatly appreciated!

Thanks in advance!

Authentication Error Adding Development Environment in DevOps Center

 

#Security

1 answer
0/9000

Hi, new to DevOps so please bear with me...

 

Trying to promot Work Item from Dev to QA and getting this error. Field does not exist on Dev org (removed by Dev) but was available as a selection.

 

Can I remove (how ?) from the committed changes so I can promote ? or is there any other workaround ?

 

#Devops #DevOps Center

 

__DEPLOY__The deployment of the work items into the next stage failed.

destructiveChanges.xml of Type CustomField failed to deploy due to No CustomField named: Account_Plan__c.User__c found

 

Type CustomField failed to deploy due to No CustomField named

3 answers
  1. Aug 4, 2025, 2:57 PM

    Mark... I know that this is an old posting but I'm also new to DevOps and was recently getting the same error. Was PULLING my hair out trying everything to figure it out. I'm posting what I did to fix in hopes it helps someone else. 

     

    My error: 

     

    Creative_Brief__c-Creative Brief Layout of Type Layout failed to deploy due to In field: field - no CustomField named Creative_Brief__c.Theme__c found 

     

    The problem is that I didn't have a custom field in the Object or on the page layout called "Theme". Since the field is not there... why am I getting this error! I'm trying to promote changes from UAT to Staging. Worked promoting to UAT so why won't it work with Staging???? 

     

    On a whim... decided to look at the XML for my page layout for Creative_Brief in Github for the branch of UAT. Guess what I found.... 

     

                <layoutItems>

                    <behavior>Edit</behavior>

                    <field>Theme__c</field>

                </layoutItems> 

     

    I downloaded the XML file as a precaution. Clicked on Edit to edit the file. Removed the code and saved. Committed the change. Tried to promote AGAIN the changes from UAT to Staging and BOOM... worked like a charm. 

0/9000

Resources from the Agentforce Ask Me Anything on Streamline Deployments with DevOps Center 

 

I hope you joined us for the fantastic Agentforce AMA on Wednesday 30 July 2025 featuring @Satya Sekhar Chegondi with product experts @Gilson Canario and @Srikrishna Padmannagari.

 

They loved answering your questions about Streamlining Deployments with DevOps Center. If you missed it, don't worry - we recorded the series and our experts have provided some great resources so you can continue your learning!

#DevOps Center #Devops #SFDC DX #Sandbox #Sandboxes #Metadata #Agentforce #Agent Builder

0/9000

Streamline Deployments with DevOps Center: Agentforce NOW Ask Me Anything July 2025 

 

DevOps Center now integrates with the new DX Inspector, a new management tool within Salesforce sandboxes that enhances metadata tracking and visualization used by Agentforce.  

 

Join developer advocate host

@Satya Sekhar Chegondi and product managers @Gilson Canario and @Srikrishna Padmannagari to learn how to easily make and track changes to metadata while configuring agents in Agent Builder. 

 

Date: Wednesday July 30, 2025

Time: 9am PT

Click here to register. 

Streamline Deployments with DevOps Center: Agentforce NOW Ask Me Anything July 2025 DevOps Center now integrates with the new DX Inspector, a new management tool within Salesforce sandboxes that enhan

 

#DevOps Center #Devops #SFDC DX #Sandbox #Sandboxes #Metadata #Agentforce #Agent Builder

0/9000

Hi,

 

We've setup an enhanced bot and while deploying the bot we're getting the following error: Invalid target dialog reference error. 

 

The bot's referencing a few messaging components as part of the dialogues. Is there any guidance on how to deploy the messaging components or would those be included in the bot itself?

6 answers
  1. Nov 5, 2023, 8:08 PM

    I've already asked Salesforce Support about this issue.

     

    I've got the following answer, maybe it helps you :

     

    "I totally understand your concern but unfortunately we cannot deploy Messaging component. However, you can create the messaging component in the target org as exactly same as in the source org. Once the messaging component is created, you can deploy the Einstein bot."

     

    In practice, it's enough if you create a component with the same name. Content is not important, just the name of the component.

0/9000