Skip to content

Commit 394f38d

Browse files
committed
Tweaks
1 parent 11663f0 commit 394f38d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

powerapps-docs/developer/data-platform/appendix-add-license-information-to-your-solution.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ In this article, the solution contains three model-driven apps (Gold App, Silver
6666
> [!div class="mx-imgBorder"]
6767
> ![Create licensing file 1](media/create-license-csv-file-1.png "Create licensing file 1")
6868
69-
To add licensing information to your solution, you need to get the **Service ID** values created in the Partner Center. You need to create these plans in the Partner Center to get the **Service ID** values. More information: [Create plans in Partner Center](/azure/marketplace/dynamics-365-customer-engage-plans).
69+
To add licensing information to your solution, you need to create plans in the Partner Center. More information: [Create plans in Partner Center](/azure/marketplace/dynamics-365-customer-engage-plans). Once you're finished creating the plans, each plan creates a **Service ID** value which is required while creating [Plan definition file](#plan-definition-file).
7070
7171
> [!div class="mx-imgBorder"]
7272
> ![Create licensing file 3](media/create-license-csv-file-3.png "Create licensing file 3")
@@ -101,15 +101,15 @@ Once you have created your own licensing CSV files, the next step is to add the
101101
102102
To add the license information from the CSV files (created above) to the solution:
103103
104-
- Open a **Developer Command Prompt for VS 2017** or higher window. NAvigate to the ___location where you have cloned solution. Enter the following command:
104+
1. Open a **Developer Command Prompt for VS 2017** or higher window. Navigate to the ___location where you have cloned solution. Enter the following command:
105105
106106
```CLI
107107
pac solution add-license -pd <path to plan definition file> -pm <path to plan mapping file>
108108
```
109-
- To check whether the licensing information is added, navigate to the ___location where you have cloned your solution zip file, you should see a new folder **ServicePlans** is created with two XML files.
110-
- Optional: To determine how the license information from the CSV files was captured, open the XML files in your favorite editor.
111-
- The **ServicePlans.xml** file contains the plan definition information from the plan definition file.
112-
- The **ServicePlansAppModules.xml** file contains the plan mapping information from the plan mapping file.
109+
1. To check whether the licensing information is added, navigate to the ___location where you have cloned your solution zip file, you should see a new folder **ServicePlans** is created with two XML files.
110+
1. Optional: To determine how the license information from the CSV files was captured, open the XML files in your favorite editor.
111+
1. The **ServicePlans.xml** file contains the plan definition information from the plan definition file.
112+
1. The **ServicePlansAppModules.xml** file contains the plan mapping information from the plan mapping file.
113113

114114
## Build the solution and create an AppSource package
115115

0 commit comments

Comments
 (0)