Skip to content

Commit 1edf421

Browse files
NkrbNkrb
committed
Indentation fixes
1 parent 40d2f1d commit 1edf421

File tree

2 files changed

+44
-44
lines changed

2 files changed

+44
-44
lines changed

‎powerapps-docs/developer/component-framework/issues-and-workarounds.md

Lines changed: 43 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -16,41 +16,41 @@ ms.topic: "article"
1616

1717
Here are some common issues that you might come across while using the Power Apps component framework and Power Apps CLI.
1818

19-
**Msbuild error MSB4036**
19+
1. **Msbuild error MSB4036**
2020

21-
1. The name of the task in the project file is same as the name of the task class.
22-
2. The task class is public and implements the Microsoft.Build.Framework.ITask interface.
23-
3. The task is correctly declared with *\<UsingTask>* in the project file or in the *.tasks files located in the path directory.
21+
- The name of the task in the project file is same as the name of the task class.
22+
- The task class is public and implements the Microsoft.Build.Framework.ITask interface.
23+
- The task is correctly declared with *\<UsingTask>* in the project file or in the *.tasks files located in the path directory.
2424

25-
**Workaround**:
25+
**Workaround**:
2626

27-
1. Open Visual Studio Installer.
28-
1. For Visual Studio 2017, select **Modify**.
29-
1. Select **Individual Components**.
30-
1. Under Code Tools, check **NuGet targets & Build Tasks**.
27+
- Open Visual Studio Installer.
28+
- For Visual Studio 2017, select **Modify**.
29+
- Select **Individual Components**.
30+
- Under Code Tools, check **NuGet targets & Build Tasks**.
3131

3232
> [!NOTE]
3333
> We will be constantly adding common issues and workarounds as we come across during the development process. If you encounter an issue and have a workaround and you think that is helpful, raise the issue [here](https://powerusers.microsoft.com/t5/Power-Apps-Component-Framework/bd-p/pa_component_framework) or raise a pull request so that we can review and add it to the list.
3434
35-
**Publisher Prefix**
35+
2. **Publisher Prefix**
3636

37-
If a component is created using the CLI version lower than 0.4.3, you will encounter an error while trying to reimport the solution file into Common Data Service.
37+
If a component is created using the CLI version lower than 0.4.3, you will encounter an error while trying to reimport the solution file into Common Data Service.
3838

39-
**Workaround**:
39+
**Workaround**:
4040

41-
- Delete the solution containing the relevant component from Common Data Service.
42-
- The component needs to be removed from the filed or grid if the component is already configured to avoid dependencies.
43-
- Import the new solution with updates to the component built by the latest CLI version.
44-
- Newly imported components can now be configured on forms or grids.
41+
- Delete the solution containing the relevant component from Common Data Service.
42+
- The component needs to be removed from the filed or grid if the component is already configured to avoid dependencies.
43+
- Import the new solution with updates to the component built by the latest CLI version.
44+
- Newly imported components can now be configured on forms or grids.
4545

46-
**Issues while updating existing code components**
46+
3. **Issues while updating existing code components**
4747

48-
1. If you get a 1ES notification asking how pcf-scripts are being used, note that these scripts are only used to build the code components but they are not bundled or used by the resulting component.
49-
2. If you have created a code component using the CLI version 0.1.817.1 or earlier and want to ensure that the latest build and debug modules are being used, make the updates to the `package.json` file as shown below:
48+
- If you get a 1ES notification asking how pcf-scripts are being used, note that these scripts are only used to build the code components but they are not bundled or used by the resulting component.
49+
- If you have created a code component using the CLI version 0.1.817.1 or earlier and want to ensure that the latest build and debug modules are being used, make the updates to the `package.json` file as shown below:
5050

51-
```JSON
52-
"dependencies": { "@types/node": "^10.12.18", "@types/powerapps-component-framework": "1.1.0"}, "devDependencies": { "pcf-scripts": "~0", "pcf-start": "~0" }
53-
```
51+
```JSON
52+
"dependencies": { "@types/node": "^10.12.18", "@types/powerapps-component-framework": "1.1.0"}, "devDependencies": { "pcf-scripts": "~0", "pcf-start": "~0" }
53+
```
5454

5555
3. Error **Failed to retrieve information about Microsoft.PowerApps.MSBuild.Pcf from remote source <Feed Url>** when the build fails for authorization issues.
5656

@@ -74,40 +74,40 @@ If a component is created using the CLI version lower than 0.4.3, you will encou
7474
</configuration>
7575
```
7676

77-
**Web resource size is too big**
77+
4. **Web resource size is too big**
7878

79-
Error **Import Solution Failed: Web resource content size is too big**.
79+
Error **Import Solution Failed: Web resource content size is too big**.
8080

81-
**Workaround**
81+
**Workaround**
8282

83-
1. When you're creating the `bundle.js` file from the CLI tooling, it bundles lot of components which makes the file large. Remove some of the components that are not necessary.
84-
2. Build the component in `production` mode by modifying the `node_modules/pcf-scripts/webpackconfig.js` file.
83+
- When you're creating the `bundle.js` file from the CLI tooling, it bundles lot of components which makes the file large. Remove some of the components that are not necessary.
84+
- Build the component in `production` mode by modifying the `node_modules/pcf-scripts/webpackconfig.js` file.
8585

86-
**Power Apps component framework Datasets getValue by property alias doesn't work**
86+
5. **Power Apps component framework Datasets getValue by property alias doesn't work**
8787

88-
Power Apps component framework dataset APIs getValue function only searches record by the dataset column name and not the property alias set in the manifest. Attempting to get value by property alias will return an empty value.
88+
Power Apps component framework dataset APIs getValue function only searches record by the dataset column name and not the property alias set in the manifest. Attempting to get value by property alias will return an empty value.
8989

90-
**Workaround**
90+
**Workaround**
9191

92-
Use the dataset column name (component can get the dataset column name by searching the column array using the alias).
92+
Use the dataset column name (component can get the dataset column name by searching the column array using the alias).
9393

94-
***Expected Behavior***
94+
***Expected Behavior***
9595

96-
```TypeScript
97-
long = dataSet.records[currentRecordId].getValue("Longitude") //based on property set in manifest"-122.3514661"
98-
```
96+
```TypeScript
97+
long = dataSet.records[currentRecordId].getValue("Longitude") //based on property set in manifest"-122.3514661"
98+
```
9999

100-
***Current Workaround***
100+
***Current Workaround***
101101

102-
```TypeScript
103-
lat = dataSet.records[currentRecordId].getValue("Address_x0020_1_x003a__x0020_Latitude")//based on the dataset column name
104-
```
102+
```TypeScript
103+
lat = dataSet.records[currentRecordId].getValue("Address_x0020_1_x003a__x0020_Latitude")//based on the dataset column name
104+
```
105105

106-
**Power Apps component framework Datasets Sharepoint issue**
106+
6. **Power Apps component framework Datasets SharePoint issue**
107107

108-
Power Apps component framework dataset component currently does not properly show the records from SharePoint. While the network request will succeed with the correct data records returned, the deserialization fails and an empty dataset is returned.
108+
Power Apps component framework dataset component currently does not properly show the records from SharePoint. While the network request will succeed with the correct data records returned, the deserialization fails and an empty dataset is returned.
109109

110-
**Workaround**
110+
**Workaround**
111111

112-
No workaround as of now. We are working on pushing a fix to our deployment trains.
112+
No workaround as of now. We are working on pushing a fix to our deployment trains.
113113

‎powerapps-docs/developer/component-framework/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Code components can be reused many times across different entities and forms. Us
4747

4848
## Licensing
4949

50-
Power Apps component framework licensing requirements are inline with existing connectors and components and is based on the type of data and connections used in your app. More information: [Power Apps pricing](https://powerapps.microsoft.com/en-us/pricing/). To align with the licensing requirements, we will be classifying code components into two types:
50+
Power Apps component framework licensing requirements are inline with existing connectors and components and is based on the type of data and connections used in your app. More information: [Power Apps pricing](https://powerapps.microsoft.com/pricing/). To align with the licensing requirements, we will be classifying code components into two types:
5151

5252
- Code components that connect to external services or data directly and not through connectors. When these components are used in an app, the app becomes premium, and end users are required to have **Power Apps** licenses.
5353
- Code components that don't connect to external services or data. When these components are used in an app that uses standard features, the app remains standard, and end users are required to be licensed at minimum for **Office 365**.

0 commit comments

Comments
 (0)