I can keep elaborating on each and every customizations and configurations in MS CRM but my goal here is to review the implementation information flow so I'll keep at it, as you can always find several online blogs that discuss various customizations and configurations within MS CRM.
A Design phase can be simple or elaborate depending upon implementation time, customer requirements and the amount of customizations and configurations from 'Simple' straightforward ones to 'Complex' Custom client-specific ones. The clearer the design phase, the quicker is the development phase of the project, else you would see yourself wind up in circles.
A good template becomes necessary here, and it is important for the client to recieve one version and the developer/application specialist to recieve another. Now, it is pertinent for the functional/solution specialist to understand customizations, configurations, and data transformations thoroughly so he/she can generate such a template.
CRM Integration can be well managed by a solutions specialist using visual products for such data transformations such as simego's CRM-Integration. Our Business Intelligence specialist works with this tool populating the tables/views out of our data warehouse and feeds them into the CRM using Simego's tool. It compares data from source or target and creates/updates as necessary, does both full & delta loads for over a million records. Will post on its performance when we use it to its complete capacity, and elaborate more on data topics when I start posting for deployment.
The development phase comprises customizations, configurations, code development and concludes with deployment to test environment. Business validation and testing is then followed by User Acceptance Testing.
I will elaborate on version control and solution management when describing the deployment phase, however, moving the MS CRM solution from the development environment to a test environment also needs to be done with care and keeping versions under control. One must pay attention to the publisher and versions under solution management in Microsoft dynamics CRM especially when you are working with more then one solution. Documenting all seperate data loads be it for products, or any other special entities thru the CRM or thru your own custom utility/tool can be a productive checklist for data loads be it test environment or production, as it will be a good staging set up/test.
CRM Solution Lifecycle Management white paper can be downloaded from here, it describes CRM solution concepts including updating layers, merge behaviors, shared publishers, solution management, hotfixes management, in a complete SDLC. The white paper also includes links to other useful downloads.
I will review local adoption groups and more in my next blog on User Acceptance Testing.
A Design phase can be simple or elaborate depending upon implementation time, customer requirements and the amount of customizations and configurations from 'Simple' straightforward ones to 'Complex' Custom client-specific ones. The clearer the design phase, the quicker is the development phase of the project, else you would see yourself wind up in circles.
A good template becomes necessary here, and it is important for the client to recieve one version and the developer/application specialist to recieve another. Now, it is pertinent for the functional/solution specialist to understand customizations, configurations, and data transformations thoroughly so he/she can generate such a template.
CRM Integration can be well managed by a solutions specialist using visual products for such data transformations such as simego's CRM-Integration. Our Business Intelligence specialist works with this tool populating the tables/views out of our data warehouse and feeds them into the CRM using Simego's tool. It compares data from source or target and creates/updates as necessary, does both full & delta loads for over a million records. Will post on its performance when we use it to its complete capacity, and elaborate more on data topics when I start posting for deployment.
The development phase comprises customizations, configurations, code development and concludes with deployment to test environment. Business validation and testing is then followed by User Acceptance Testing.
I will elaborate on version control and solution management when describing the deployment phase, however, moving the MS CRM solution from the development environment to a test environment also needs to be done with care and keeping versions under control. One must pay attention to the publisher and versions under solution management in Microsoft dynamics CRM especially when you are working with more then one solution. Documenting all seperate data loads be it for products, or any other special entities thru the CRM or thru your own custom utility/tool can be a productive checklist for data loads be it test environment or production, as it will be a good staging set up/test.
CRM Solution Lifecycle Management white paper can be downloaded from here, it describes CRM solution concepts including updating layers, merge behaviors, shared publishers, solution management, hotfixes management, in a complete SDLC. The white paper also includes links to other useful downloads.
I will review local adoption groups and more in my next blog on User Acceptance Testing.
No comments:
Post a Comment