Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Adding existing Components to a new Solution

  • 1.  Adding existing Components to a new Solution

    SILVER CONTRIBUTOR
    Posted 14 days ago
    Hello All,

    I have recently been reading up on how to create custom Solutions to segment customizations within their own Solution, rather than updating/altering the Core Solution that comes OOB. I've learned there are obvious reasons for this however, I have been looking online for a solid walkthrough and found nothing. Here is my scenario;

    1. Creating a POC for a "fresh/clean" instance to clean up the environment (already created)
    2. I have created 2 "module" Solutions; one for Sales Entities, and one for Customer Service Entities (we are on newest Dynamics 365 v9.x)
    3. I have created a custom Publisher for said Solutions and the new Solutions were created with the new Publisher

    However, this is where I am stuck. I understand that I can import "Existing Components" into the new Solutions I have created, but there is no documentation that I can find (or rather step-by-step/explanation) regarding how to go about adding the proper data to the new Solution so I can update it. Essentially, I have created these new Solutions for any Customizations that we wish to implement into our Sales module of the Core Solution or the Customer Service module of the Core Solution. When I "Add Existing Entity", it provides some simple information I'm able to follow, however, when it comes to adding the "Entity Metadata" or the "Assets" is where it loses me.

    If I am just creating this new Custom Solution to append/update the Core Solution components (basically adding Fields/Form Customizations/Views/etc) what do I actually need to bring over? Would it just be the Metadata or both the Metadata AND the Assets? Is there a danger to doing one over the other? Any advice would be helpful.

    Thank you,


    ------------------------------
    Nicholas Arbour
    TEKLYNX
    Whitefish Bay WI
    ------------------------------


  • 2.  RE: Adding existing Components to a new Solution

    SILVER CONTRIBUTOR
    Posted 14 days ago

    Hi Nicholas,

    Good thing that you do not use the core solution!

    One major thumb rule when working with solution is : Include the minimum required, that is only what you have configured.

    For new custom entities, this means include everything, All assets and metadata.

    For custom in existing entities, this means :

    - always uncheck "Add all assets"!
    - then add selectively only what you will customize (specific forms, views, fields etc...).
    - regarding entity metadata, you should include it if you need to change general information of the entity, that appears here :


    By default, I prefer not to include Entity metadata, but you can always include it if you prefer.

    Best Regards,



    ------------------------------
    Laurent Maneville
    Nmédia
    Drummondville QC
    ------------------------------



  • 3.  RE: Adding existing Components to a new Solution

    Posted 14 days ago

    Hi Nicholas,

    Also consider working through what I consider the D365CE Customization Bible. The Solution Lifecycle Management whitepaper https://www.microsoft.com/en-us/download/details.aspx?id=57777

    Has some really good content around building Solutions for different scenarios.



    ------------------------------
    Jaco Kofman
    Microsoft
    Redmond WA
    ------------------------------



  • 4.  RE: Adding existing Components to a new Solution

    GOLD CONTRIBUTOR
    Posted 11 days ago
    Hello Jaco,

    Thank you for sharing the whitepaper link . That is one great piece of information.
    I had a request around the same , do you have any other links as well which talks about different parts of CRM.
    If there is a way wherein we could get updated documentation which are whitepapers for Dynamics CRM that would be awesome .

    if you could share those links or the link to the repository that would be awesome .

    ------------------------------
    Bhartendu Pandey
    Willis Towers Watson
    London
    ------------------------------



  • 5.  RE: Adding existing Components to a new Solution

    Posted 10 days ago
    Hi Bhartendu,

    When you say 'talks about different parts of CRM' are you talking about from an end-user point of view?  If yes then the best place is still https://docs.microsoft.com/en-za/dynamics365/ for the most comprehensive (and up-to-date) information around all things Dynamics 365.  Hope this helps.

    ------------------------------
    Jaco Kofman
    Microsoft
    Redmond WA
    ------------------------------



  • 6.  RE: Adding existing Components to a new Solution

    GOLD CONTRIBUTOR
    Posted 8 days ago
    Hello Jaco,

    Thank you for sharing the link , I was thinking more from the perspective of Consultants wherein we could have similar updated documentation regarding various topics in CRM for eg white paper on Setting up Outlook App , Or white paper on Field service and project services etc. .. is there a place wherein we could get those articles.

    thank you for your inputs :-)

    ------------------------------
    Bhartendu Pandey
    Willis Towers Watson
    London
    ------------------------------



  • 7.  RE: Adding existing Components to a new Solution

    MICROSOFT MVP
    Posted 14 days ago
    Hi Nicholas

    I wanted to zero in on your comment "how to go about adding the proper data"

    To be clear, the solutions will move configurable assets like entities, fields, etc.  Solutions cannot move "data" (like "jim" or "bob" contact records).

    In this case "entity metadata" are entity settings options such as if document management is enabled, etc.

    Not sure if that was the core of your question; if you wanted to move actual data for testing/development, you would need to use the standard import/export process or other data migration tools.

    Cheers
    Nick




    ------------------------------
    Nick Doelman
    Microsoft MVP
    Dynamics 365 Specialist
    Nick Doelman Co.
    ottawa ON
    ------------------------------



  • 8.  RE: Adding existing Components to a new Solution

    SILVER CONTRIBUTOR
    Posted 14 days ago
    Hi Nicholas,

    As an addition, you will find an overview of crm solutions in MS documentation here:
    https://docs.microsoft.com/en-us/dynamics365/customer-engagement/customize/solutions-overview

    This is more the 'big picture'; Fellows here gave you more detailed answers.

    ------------------------------
    Fabien Bernard
    CRM Developer
    Montréal QC
    ------------------------------



  • 9.  RE: Adding existing Components to a new Solution

    TOP CONTRIBUTOR
    Posted 14 days ago
    Include the entity metadata. If you don't the system will disable and re-enable auditing, which screws up your audit history.

    ------------------------------
    Ryan Perry
    Business Systems Analyst
    Auric Solar
    ------------------------------



  • 10.  RE: Adding existing Components to a new Solution

    SILVER CONTRIBUTOR
    Posted 13 days ago
    Hello All,

    Thank you for the advice regarding how to properly go about doing this. I appreciate it greatly. As for my comment on the "proper data", still learning the terminology associated with Solutions so I'm not quite on point with that yet. But, your answers were basically spot on to what I was getting at.

    There are going to be some settings changes I would like to make to the core Entity regarding whether or not documents/auditing/OneNote/etc options are shown, so I would like to include the Metadata. I have just recently connected our tenant to SharePoint, I do understand that within the Dynamics Admin page you can see that there is a separate database to store "Files" instead of everything within one database like it was previously (appreciated Microsoft). But, being able to utilize the files uploaded to SharePoint through Dynamics, or snag that file through Outlook via SharePoint, or even to utilize the file within a custom PowerApp, etc.. I thought it was a really cool feature to test out and see what we could do with it.

    Also, thank you for the link to the ALM PDF paper, funny enough, I have actually read though that a couple times to get a grasp on the concepts I started learning about (which prompted my questions here). It does an amazing job of laying out proper practices and common pitfalls (to which I was not aware I was doing by not utilizing segmentation of Solutions!). Needless to say, it's been very helpful.

    However, the additional information given here has also been extremely helpful. I'm glad to now know that "IF" I wish to update a particular Form/View/Chart/etc. it must be included in the Assets portion of the import (which I imagine I can always import later, if not done within the initial import, if necessary?) for me to make changes in the new Solution to alter the functions of the Core Solution.(I think I'm stating that correctly). I definitely have some more learning to do in this area and I appreciate all the advice. Thanks again gents.


    ------------------------------
    Nicholas Arbour
    TEKLYNX
    Whitefish Bay WI
    ------------------------------



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