web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Question on solution best practice idea

(0) ShareShare
ReportReport
Posted on by 65

Hi there, my team is going to do production deployment for our client soon. So, i stumble upon a question which we have to export and import the solution as managed solution in the production which is pretty standard. However, my question is that we have too many components under one solution, such as ARC, SLA, cloud flow, entities and so on. Having these much of components in one solution triggered my concern where if we want to make changes to any of the components as "managed solution" would require us to reimport the whole solution again to the production. Example of scenario would be, if i want to remove a column from an entity, i have to import the whole solution just to stage for update in order to remove the column from production.

My idea is that, would it be better for me to separate it into different solution such as Entity solution, SLA Solution, ARC Solution. So that if i have changes for example on entity related changes, i just have to import the entity solution without need to touch SLA and ARC. 

I have the same question (0)
  • Suggested answer
    Abdul Wahab Profile Picture
    12,119 Moderator on at

    Hi Low Chen THye,

    If you break components into different solutions. How can you handle dependency? I am interested to know the answer.

    What about the 'clone a patch' feature?

    What about just bringing that table separately instead of taking the solution with the whole components?

    Sorry, If it doe not makes sense.

  • Low Chen THye Profile Picture
    65 on at

    I agree with you that handling of dependency would be tougher if we split into multiple solution. Just that i have one question, if i remain with deploy one solution that include all the components to the production. Let say i want to remove one column from an entity in production, how can this be achieved without import the whole solution? Any suggestions are welcomed.

    Can you elaborate on the "What about just bringing that table separately instead of taking the solution with the whole components?" ?

  • Suggested answer
    Abdul Wahab Profile Picture
    12,119 Moderator on at

    HI Low Chen THye,

    I do not think there is any other recommended way rather than splitting the solution in the first import but I am wondering about the dependencies. In my opinion, the split would be easy if we first bring/import tables only. What do you think?

  • Low Chen THye Profile Picture
    65 on at

    1st solution A(entities,form,script etc)

    2nd solution B(cloud flow, ARC, sla etc)

  • Suggested answer
    Abdul Wahab Profile Picture
    12,119 Moderator on at

    Hi Low Chen THye,

    Looks perfect.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 108 Super User 2025 Season 2

#2
Jimmy Passeti Profile Picture

Jimmy Passeti 50 Most Valuable Professional

#3
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 49 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans