Skip to content

Commit ea6c574

Browse files
authored
Merge pull request MicrosoftDocs#3344 from MicrosoftDocs/Nava_issues
Updating links
2 parents ce076db + e2dd8ea commit ea6c574

File tree

3 files changed

+4
-4
lines changed

3 files changed

+4
-4
lines changed

powerapps-docs/developer/component-framework/implementing-controls-using-typescript.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -384,7 +384,7 @@ Follow these steps to create and import a [solution](https://docs.microsoft.com/
384384
> - Under **Code Tools**, check **NuGet targets & Build Tasks**.
385385

386386
6. The generated solution zip file is located in the `Solution\bin\debug` folder.
387-
7. Manually [import the solution into Common Data Service](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) using the web portal once the zip file is ready or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools).
387+
7. Manually [import the solution into Common Data Service](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) using the web portal once the zip file is ready or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools).
388388

389389
## Adding code components in model-driven apps
390390

powerapps-docs/developer/component-framework/import-custom-controls.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ To create and import a solution file:
4747
> - If you encounter an error that says *Ambiguous project name* when running the `msbuild` command on your solution, ensure that your solution name and project name are not the same.
4848
4949
4. The generated solution files are located inside the `\bin\debug\` folder after the build is successful.
50-
5. Manually [import the solution into Common Data Service](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) using the web portal or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerApps-BuildTools).
50+
5. Manually [import the solution into Common Data Service](https://docs.microsoft.com/powerapps/maker/common-data-service/import-update-export-solutions) using the web portal or automatically using the [Microsoft Power Platform Build Tools](https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.PowerPlatform-BuildTools).
5151

5252
## Connecting to your environment
5353

@@ -91,7 +91,7 @@ The `push` capability speeds up the inner-developer cycle development because it
9191
To use the `push` capability, do the following:
9292
9393
1. Ensure that you have a valid authentication profile created.
94-
2. Navigate to the root directory where the code component project is created.
94+
2. Go in to the folder where you have created the code component project.
9595
3. Run the command.
9696
9797
```CLI

powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Utility/getGlobalContext/isOnPremises.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ search.app:
1414
- PowerApps
1515
- D365CE
1616
---
17-
# isOnPremise (Client API reference)
17+
# isOnPremises (Client API reference)
1818

1919

2020

0 commit comments

Comments
 (0)