Skip to main content Join us at TDX in San Francisco or on Salesforce+ on March 5-6 for the Developer Conference for the AI Agent Era. Register now.

#Devops8 discussing

Multiple developers working on the same components will override each other's changes when using copado . How to avoid these type of issues ? 

 

#Salesforce Developer #Devops #Best Practices #Copado

1 answer
  1. Today, 12:45 PM

    Hi @Pami Reddy Praswanth Kumar

     

    To avoid issues where multiple developers override each other's changes when working on the same components in Copado, Below are some best practices:

     

    1. Use Version Control:

    •   Implement a robust version control system (VCS) like Git. Ensure all developers are familiar with branching strategies such as feature branches, develop branches, and release branches.

    2. Branching Strategy:

    • Adopt a clear branching strategy. For example, use feature branches for individual tasks and merge them into a develop branch once they are complete and tested.

    3. Frequent Commits and Pulls:

    • Encourage developers to commit their changes frequently and pull the latest changes from the repository regularly. This helps in identifying conflicts early.

    4. Code Reviews:

    • Implement a code review process. Before merging changes into the main branch, have another developer review the code to catch potential conflicts and ensure code quality.

    5. Continuous Integration (CI):

    • Use CI tools to automatically test and merge changes. This ensures that the integrated code is always in a deployable state.

    6. Communication:

    • Maintain clear communication among team members. Use tools like Slack or Microsoft Teams to keep everyone updated on what they are working on.

    7. Locking Mechanism:

    • Use a locking mechanism in Copado to prevent multiple developers from working on the same component simultaneously. This can help avoid conflicts.

    8. Change Sets Best Practices:

    • Change sets are a great way to package Salesforce metadata changes for deployment. It’s essential to ensure they are well-documented and that all dependencies are included.
    • Before deploying, the change set should be thoroughly reviewed to ensure that there won’t be conflicts or unexpected issues in the target environment.

    Hope this helps. Thanks!

     

0/9000

DevOps for Data Cloud: Salesforce Developers Ask Me Anything January 2025

 

Join developer advocate host @Danielle Larregui in conversation with product managers @William Yeh, @Karen Fidelak and @Rohit Mehta on all things #Data Cloud #Devops. They’ll share how to build apps with @* Data Cloud * using application lifecycle management (ALM) phases, tools, Data Cloud-specific sandboxes and packaging, and #DevOps Center integration. Don’t miss the live Q&A and get your technical questions answered!

 

Date: Wednesday January 29, 2025

Time: 9am PT

Registration: https://www.linkedin.com/events/7272350236822368256

DevOps for Data Cloud: Salesforce Developers Ask Me Anything January 2025 Join developer advocate host in conversation with product managers , and on all things .

4 comments
0/9000

Resources from the Salesforce Developers Ask Me Anything on DevOps for Data Cloud

 

I hope you joined us for the fantastic #SFDevsAMA on Wednesday 29 January 2025 featuring Developer Advocate @Danielle Larregui hosting product managers @Rohit Mehta, @William Yeh and @Gilson Canario.

 

Our experts loved answering your questions about #Devops for Data Cloud. If you missed it, don't worry - we recorded the series and our experts have provided some great resources that our experts for you to continue your learning!  

 

And don't forget, you can find all the recordings from our back catalog of Ask Me Anything sessions on our dedicated playlist on our Salesforce Developers YouTube channel

1 comment
0/9000

When deploying a work item containing a flow with the repeater element I am encountering an error:

 

Error:

The Repeater screen component isn’t supported in this API version. To retrieve or deploy this flow, use API version 60.0 or later.Error when moving Flow containing Repeater in DevOps

I have tried it with the flow both with API version 61 and 62 I got the same error.

FLow APIversion.pngAny tips? Besides using a change set :)

 

#DevOps Center  #Devops

13 answers
0/9000
2 answers
  1. Dec 19, 2024, 4:13 PM

    Does anyone have a practical example of how to send a test report to Sonar using sonar.apex.coverage.reportPath (reference) before deployment metadata without running Apex Tests validation twice? 

     

    As of now, my understanding is that it is necessary to execute sf apex run test via CLI and then sf apex get test to generate the output file and send the report to SonarQube.

     

    #Devops #Ci/cd #CICD

0/9000
2 answers
  1. Sushil Kumar (UKG) Forum Ambassador
    Dec 10, 2024, 11:22 AM
    You can try data loader - https://help.salesforce.com/s/articleView?id=000382372&language=en_US&type=1 or some middleware like informatica/mulesoft. I have used informatica in the past for file migration.
0/9000

🚀 Introducing Simple SF CLI: Supercharge Your Salesforce Deployments!

 

I'm excited to share my recent side project: Simple SF CLI, a lightweight 11 kb, Node.js-powered command-line tool crafted to simplify and accelerate Salesforce DX (SFDX) workflows. With this tool, you can:

 

1. 🛠️ Convert, package, and deploy in just 5-7 seconds, far faster than installing Salesforce CLI or SGD.

2. 🚫 Skip the need for Salesforce CLI or additional plugins.

3. 🔗 Seamlessly integrate it into CI/CD pipelines like bitbucket, github etc.,

 

This pet project is designed to streamline your workflow and save time for developers and admins alike. Give it a try!

 

#sfcli #devops #sf #sfdx

 

Want to see it in action? go ahead and install simple-sf-cli

 

#Salesforce Developer  #SFDX CLI  #Salesforce

0/9000

I'm unable to promote a work item in DevOps. I made a small change to a flow, however am getting an error after attempted promotion from a Metadata Sandbox to our Partial Copy: "The Repeater screen component isn’t supported in this API version. To retrieve or deploy this flow, use API version 60.0 or later."

 

Notes

API versions: the flow was already at API version 60.0, but I updated the flow API version to 61.0 in my sandbox and partial copy in case that was the issue. Still getting the same error.

 

Repeater Screen component: The repeater screen component was already built, deployed, and working just fine. The update I made to the flow had nothing to do with the repeater screen component. I'm just not able to push my update through because the system isn't recognizing that the API version is up to date?

5 answers
0/9000

🖥️ Now LIVE: Dreamforce Developer Sessions on YouTube

 

Catch up on must-see sessions from #Dreamforce2024. Watch Salesforce product experts, Developer Advocates and fellow Trailblazers dive deep into the hottest topics, including Agentforce and Data Cloud, share best practices, and more! Check out these 3 Dreamforce ‘24 playlists:

 

Agentforce and Data Cloud | Dreamforce ‘24 playlist

Catch up on technical Agentforce and Data Cloud sessions from Dreamforce 2024. Get the latest on Agentforce, Agent Builder, Prompt Builder, Model Builder, and Data Cloud in deep-dive developer sessions.

Click here to watch now 

 

Salesforce Platform and App Dev | Dreamforce ’24 playlist

Dive deep into technical Salesforce Platform development sessions from Dreamforce 2024. Whether you’re new to Salesforce or an experienced developer, this curated playlist will give you everything you need to build on the Salesforce Platform.

Click here to watch now 

 

Salesforce Tools and DevOps | Dreamforce ’24 playlist

Tune into technical Salesforce tools and DevOps sessions from Dreamforce 2024. This playlist is full of best practices and resources to help you deliver applications and experiences.

Click here to watch now 

 

Want More? Subscribe to the Salesforce Developers YouTube channel!

🖥️ Now LIVE: Dreamforce Developer Sessions on YouTube Catch up on must-see sessions from .  #Agentforce #Retrieval Augmented Generation (RAG)  #DevOps Center #AI #LLM #Tableau Integration #LWC #Apex 

0/9000

Hello,

 

I'm trying to understand what are the best practices when working on a project that has  Omnistudio components (FlexCards, IP, Omniscript, etc.). Is it advisable to have a scratch org for every developer when doing their customisation or a common Dev Org or one dev box per developer? What is recommended? What are the challenges and considerations of different approaches especially from omnistudio point of view?

 

Thanks,

Neelesh

 

#Omnistudio #Deployment #SFDX CLI #Devops #Salesforce Developer

1 answer
  1. May 5, 2024, 2:02 AM

    Recommended Approach - Development Org with Version Control:

    Use a single Developer Org shared among your development team. This allows for: 

    Collaboration: Developers can easily share and test Omniscripts, FlexCards, and other components.

    Consistency: Ensures everyone is working on the same codebase and avoids versioning issues.

    Implement a robust Version Control System (VCS) like Git: 

    Track changes, revert to previous versions if needed.

    Manage concurrent development and avoid conflicts.

    Challenges of Scratch Orgs for Omnistudio:

    • Limited Functionality: Scratch orgs lack features crucial for Omnistudio development, such as:
    • OmniStudio Metadata API: This API allows deploying and retrieving Omniscript components between orgs. Not available in scratch orgs.
    • DataRaptor Actions: DataRaptor actions are custom code snippets used within Omniscripts. Scratch orgs lack the security model to support them.
    • Deployment Overhead: Frequent deployments from scratch orgs to a testing or staging org become cumbersome and inefficient.

    Hope this helps

0/9000