Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

What's your preferred way of naming and managing solutions?

  • 1.  What's your preferred way of naming and managing solutions?

    Posted 8 days ago

    I have finally developed an SDL process for our org and my last task is to determine a naming convention for our solutions. We'll be going with unmanaged solutions in all envs because of our size and small team (aka, me).

    My question is, how do you name your solutions? So far we're thinking "SOL-CE####-INT-DESC" where we ID it as a solution for our DB sake, then note that it's a CE solution with a sequential number, then the initials of the developer, then a short description. So it could look like this: SOL-CE0004-ABC-NewContactViews. We'd also of course add a fuller description in the description field for the solution but being able to see at a glance what's in a solution is helpful.

    However, my main concern with this is that I'd have to keep each solution to one main customization. I'm fine doing that but wanted to get other opinions on the matter, especially regarding how to manage the number of customizations per solution. And I know there's no one right answer but I'm sure some are better than others!



    ------------------------------
    Lucas Hewitt
    Enterprise Application Specialist
    Ethnos360
    ------------------------------
    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 2.  RE: What's your preferred way of naming and managing solutions?

    TOP CONTRIBUTOR
    Posted 7 days ago
    Lucas,
    It sounds like you've got a very organized system for your naming your solutions.
    For my organization, I do keep solutions to one main customization. It makes the solutions small, easy to release, and each one has minimal impact on users. When going Unmanaged, it makes solutions easier to pull back if you want to change. I name my solutions according to the main entity affected and the change (e.g., Contact_PackagingPref if I'm adding shipment packaging preferences to a Contact). I store the solutions in Azure DevOps Repository where I can enter a brief description of the solution and developer name when I commit.

    ------------------------------
    Allison Briden
    Business Systems Analyst
    Energy Trust of Oregon
    Portland OR
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 3.  RE: What's your preferred way of naming and managing solutions?

    Posted 6 days ago
    Our org is transitioning from a very chaotic system so the more order and organization the better!

    And it's good to hear from someone else that they're already doing bite-size solutions. The benefits that you listed make a lot of sense. We're not currently using a repo since we're in such early stages, hence the longer, more detailed name.

    ------------------------------
    Lucas Hewitt
    Enterprise Application Specialist
    Ethnos360
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 4.  RE: What's your preferred way of naming and managing solutions?

    TOP CONTRIBUTOR
    Posted 3 days ago
    @Allison Briden - we are doing something similar.  How do you prevent a large number of solutions in your production environment, since you are importing a different one for every single change?  Or does it matter?  Over time I would think we would want to clean up all the different solutions that get added to the production environment continuously over time? ​

    ------------------------------
    Shawn Hickey
    Burns & McDonnell
    Kansas City MO
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 5.  RE: What's your preferred way of naming and managing solutions?

    TOP CONTRIBUTOR
    Posted 2 days ago
    Lucas,

    We name them based on the project, not very formal, but it works.  We don't allow solutions to be renamed after they are created either.  Only objects that are changed or added are included in the solution, not one object more or less, no excuses.  What i also require is in the description of the solution it states every object in the solution and what was done to it, also any notes on what needs to be done to the destination environment before and after the solution import (this covers things not done in a solution like import/update data and deletion of objects).  When the solution moves to production the solution description it copied into a log and the solution file is kept as well.  Since the solutions are unmanaged there is no reason to keep them in production, once a solution is in production for a while, usually about 6 months, it is deleted.

    The toughest challenge we have had with moving solutions is when there are multiple projects running that impact the same entity.  We try to avoid this or try to get projects lumped/delivered together.  Other than this, our process seems to be working.

    Hope this helps,

    ------------------------------
    Jim Corriveau
    A.W. Chesterton Company
    Groveland MA
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 6.  RE: What's your preferred way of naming and managing solutions?

    TOP CONTRIBUTOR
    Posted 2 days ago
    I delete the oldest solutions in CRM and leave in the more recent ones. As the solutions are all Unmanaged, the changes are added to the Default Solution and removing the solution does not remove the customizations.

    ------------------------------
    Allison Briden
    Business Systems Analyst
    Energy Trust of Oregon
    Portland OR
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 7.  RE: What's your preferred way of naming and managing solutions?

    GOLD CONTRIBUTOR
    Posted 2 days ago
    @Allison Briden, I am looking for your input on unmanaged solution revision management as I am following the same path you are describing. I am releasing small solutions also, but what do you mean by "I do keep solutions to one main customization" . You have one main solution that you are making customizations to, or just keep adding multiple solutions to production from dev. Can you please clarify. Thanks so much for sharing.



    ------------------------------
    Emilia Scott
    Data Architect
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 8.  RE: What's your preferred way of naming and managing solutions?

    TOP CONTRIBUTOR
    Posted 2 days ago
    @Emilia Scott I create many small solutions. Each solution typically customizes just one entity/table but may involve more. The customization usually serves one User Story in Azure DevOps.


    ------------------------------
    Allison Briden
    Business Systems Analyst
    Energy Trust of Oregon
    Portland OR
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 9.  RE: What's your preferred way of naming and managing solutions?

    SILVER CONTRIBUTOR
    Posted 2 days ago
    Hi All,

    My solution approach is a little different than what I've read here! For a naming convention, I took a simple approach, the display name is a date:  Solution 2021-1-18, for example. I manage releases as 2-4 week sprints, so all the changes I've made during that timeframe go into that unmanaged solution. Each change is listed in the "Information" section and also documented using Azure DevOps.

    One question I have - the App Designer doesn't appear to have an "Information" area to list out the changes... has anyone found a way to include explanations of changes when using that method of making changes?

    Thanks for sharing - the responses have been very interesting!

      Teri

    ------------------------------
    Teri Stora
    CRM Manager
    TGG Solutions
    Grand Rapids MI
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 10.  RE: What's your preferred way of naming and managing solutions?

    GOLD CONTRIBUTOR
    Posted 2 days ago
    Hi Teri,
    Are you using unmanaged in Production also? So am I understanding correctly - every 2-4 weeks you export an unmanaged solution into Production? How about in dev, the same amount of mini solutions? Or you use Clone Solution?
    The reason I am asking because I am looking to do the same thing and I am trying to understand all the options presented in this thread.
    Thanks so much for your input.

    ------------------------------
    Emilia Scott
    Data Architect
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 11.  RE: What's your preferred way of naming and managing solutions?

    SILVER CONTRIBUTOR
    Posted 2 days ago
    @Emilia Scott I haven't looked into Clone Solutions yet... if someone has experience using it, I'd be interested in learning about any pros/cons.

    I create the solution in DEV and push it to QC for testing and then on to Production - the same solutions exist in all three. Every release to production includes sending out Release Notes that document the enhancement and fixes. It is the business's responsibility to update the end users' operational guides.

    -Teri

    ------------------------------
    Teri Stora
    CRM Manager
    TGG Solutions
    Grand Rapids MI
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


  • 12.  RE: What's your preferred way of naming and managing solutions?

    SILVER CONTRIBUTOR
    Posted 16 hours ago
    We use JIRA to track all of our functionality changes, so we create 1 solution per JIRA task/story in our development environment (named the same so we can go back and reference). We deploy each "bite size" solution to our QC environment, and then we create a new solution in QC that holds all the "bite size" customization changes. This solution is named the same as our release in JIRA, and it is moved to our staging environment for final validation before being deployed to production on our scheduled release date. We release new functionality/updates/enhancements every 4 weeks. After releases, we can delete the solutions since they're unmanaged and the changes are applied to the default solution.

    ------------------------------
    Libby George
    Sr. CRM Sales Analyst
    Milwaukee Tool
    Brookfield WI
    ------------------------------

    Digital Acceleration Binge Day.  January 28th 2021 | 11:00 AM - 2:00 PM EST


If you've found this thread useful, dive deeper into User Group community content by role