Dynamics 365-about solution (III)

This article is about Solution usage suggestions. If you have some practical suggestions, please leave a message to discuss them.

I. Version Control

Solution has a version number. When you create a new solution, you may assign a value of 1.0 directly, so you don't need to worry about it anymore. However, here is a simple description of the MS-style version number, which is generally the four numbers separated by ".": Main version number, subversion number, compile version number, and modify version number. The last two versions are optional or interchange locations. The first two are required. We recommend that you design and manage the solution version number during the iteration cycle. The benefits in this area are not repeated. After all, you can understand whether it is development or not.

Ii. Classification

Classification is to better manage solution. We know that there are many types of Components in CRM, and in solution, if you put all the components in a solution, you will find that the later, the more difficult your solution is to maintain. So can I simply split the components from the quantity? For example, I split a lot of workflow, plugin, and entity into multiple solutions. This is not the case. Here we talk about different categories. We can generally consider these aspects:

1. component type

2. businesses involved in component: including business logic and business departments

3. Component dependency

4. Number of component

5. Relationship between component and project Iteration

Currently, Ms products adopt a modular design concept. Therefore, this modularization is applied to solution. For example, you need to consider which solutions can be planned into a "module". After deployment, customers will not need it in the future, you can directly Delete the product without affecting the current business (check that the solution product in the current appsource can be deleted without affecting the environment structure, implemented solution import and deletion); which solution belongs to XX department, and can be updated without affecting the business of other departments even if solution is updated in the future; which solutions depend on other solutions, and whether the dependent solution is designed to be more common.

3. Download logs

Generally, if the solution import succeeds or fails, the download log option is available. By using this log, we can accurately and efficiently locate the component with errors and possible causes.

　　1. Import failed

Do not use NotePad to open the downloaded log file, so that you will see the confidential information, not intuitive. UseExcelOpen log and you will find that all component information, status information, and comments information are organized, so that you can easily find the failed component and failure description, to help us solve the problem. One thing to note is that the CRM import operation is to modify data in the database, so there will be a very helpless situation: Even if you have more solution problems, CRM only exposes one problem once it is imported, rather than exposing all the problems at a time as if there is a statistical list.

　　2. Import successful　　

Many people may see that the CRM shows that the solution has been imported successfully, so they close the window and feel that the log is dispensable. We recommend that you save the log even if the import is successful. There are two reasons: on the one hand, even if the import is successful, there may be a lot of warning information, and some warning information may even affect subsequent operations. For example, if you update the workflow solution and the import is successful, why does workflow activate fail? If you view the warning information of the imported log, you may find a message indicating that "workflow involves the user which does not exist in the current environment ......". The other reason is that if there is an environmental problem in the future because of this solution, it can also be used as a basis for solving the problem.

　　3. import ing

　　Generally, the log option is downloaded for importing solution. If the hardware resources are insufficient or the solution itself is too complicated, it may happen that the progress bar is stuck at about 85% at the end, and then there is no response. In this case, you can check the version number of solution to check whether the solution is successfully imported. Of course, there will be no log download operations at this time.

Dynamics 365-about solution (III)