Customer Engagement & Dynamics CRM Forum

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!

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!

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!

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!

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!

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!

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!

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!

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!

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!

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!