Merge pull request #2295 from MicrosoftDocs/grhurl-pcf-docs-faqs

FAQ updates for PCF Docs effort

Author: Nkrb

powerapps-docs/developer/component-framework/faq.md

@@ -1,34 +1,63 @@
 ---
-title: "FAQ | MicrosoftDocs"
+title: "FAQs | MicrosoftDocs"
 description: "Frequently asked questions about component framework"
 manager: kvivek
 ms.date: 10/01/2019
 ms.service: "powerapps"
 ms.topic: "index-page"
 ms.assetid: 9f940264-d7d5-4930-8052-1bd582445d37
-ms.author: "nabuthuk"
-author: Nkrb
+ms.author: "grhurl"
+author: ghurlman
+ms.reviewer: nkrb
 ---
 
-# FAQ
+# FAQs
 
 [!INCLUDE[cc-beta-prerelease-disclaimer](../../includes/cc-beta-prerelease-disclaimer.md)]
 
-## Multiple components in single manifest file
+### Component changes are not reflected after the updated solution import?
 
-It is not possible to define multiple components in a single manifest file. 
+Update the component version (minor or patch) in the component manifest file (for example, 1.0.0 to 1.0.1). 
+Every update in the component needs a component version bump to be reflected on the Common Data Service server.
 
-## Calling Processes/Actions
+> [!NOTE]
+> - A new solutio must be created everytime if you wish to have a major version bump. Incrementing the major version number (eg 1.0 to 2.0) is not supported as an upgrade.
+> - Only three version sections are supported (i.e. MAJOR.MINOR.PATCH). These version number sections should be between 0 and 65536.
 
-This is not supported. As of today, you can only call dialog boxes using the [Navigation](reference/navigation.md) method.
+### What are the things to be considered from a performance perspective?
 
-## Calling components within another component
+1. If you wish to access large chunk of data items, implement [filtering](reference/filtering.md) and [paging](reference/paging.md) methods to limit how much data should be loaded.
+2. Batch your network calls, and make any network calls asynchronous. Design the component in such a way that all the required information is provided with a single call. 
+3. Design the component such that the user has to perform an action (such as clicking on a button) to initiate the loading of specific item's data rather than making the call for each data item.
+4. Ensure that you clean up the resources using the [destroy](reference/control/destroy.md) function. Open network calls, connections, and event handlers need to be cleaned up to increase the performance.
 
-This is not supported.
+### Where can I find some good examples of code components?
 
-## Font Resource
+Lots of great examples from the community are available on the [Power Apps Community Forums](https://powerusers.microsoft.com/t5/Power-Apps-Component-Framework/Community-content-sample-components-blogs-etc-Link-to-this-page/td-p/280710).
 
-Currently font resource (.tff) is not supported in Power Apps component framework.
+### How to use rich data types in code components such as Collections?
+
+Currently, this feature is not supported. However, there is a [JSON function](https://docs.microsoft.com/powerapps/maker/canvas-apps/functions/function-json) in canvas-apps that allows app makers to stringify their data.
+
+1. Pass the collection into the JSON function.
+2. Pass the string representation of the collection data that is returned from the JSON function into one of the component's string properties.
+3. Use [JSON.parse](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/parse) in the component code to convert it back into a JavaScript Object.
+
+### How can I define multiple components in a single manifest file?
+
+Defining multiple components in a single manifest file is not supported. 
+
+### How can I define behavior properties?
+
+This is not supported at this time. Currently, you can only call dialog boxes using the [Navigation](reference/navigation.md) method in model-driven apps.
+
+### How can I call other components from within another component?
+
+This is not supported natively by the framework. You can use one of many third-party libraries to enable this functionality in your components.
+
+### Can I bundle font resources?
+
+Currently, font resources (files with a .ttf file extension) are not supported by the framework.
 
 ## Related topics
 

powerapps-docs/developer/component-framework/limitations.md

@@ -20,10 +20,6 @@ With the release of Power Apps component framework, you can now create your own
 
    > [!NOTE]
    > Support for shared libraries across components using library nodes in the component manifest is not yet supported. We are reviewing this and will be adding this capability in future release.
-4. Defining multiple components in a single manifest file is not yet supported.
-5. Calling out processes and actions are not supported yet. You can only call dialog boxes using the [Navigation](reference/navigation.md) method.
-6. Calling one component  from another code component is not yet supported.
-7. Currently font resource (.tff) is not yet supported.
 
 ## Related topics
 

powerapps-docs/developer/component-framework/toc.yml

@@ -34,6 +34,8 @@
       href: issues-and-workarounds.md
     - name: Limitations
       href: limitations.md
+  - name: FAQs
+    href: faq.md
   - name: Sample components
     items: 
     - name: How to use the sample components?

powerapps-docs/developer/component-framework/use-sample-components.md

@@ -29,20 +29,22 @@ Follow the steps below to import and try the sample components in your model-dri
 1. Navigate to the folder on your computer where you have downloaded the sample components, and extract the .zip file.  
 1. Open Developer Command Prompt for Visual Studio 2017 and navigate to the sample component folder in the extracted folder that you want to see it in runtime. For example, navigate to the \<extracted_folder>/TS_IncrementComponent folder.
 1. Run the following command to get all the required dependencies:
-    ```
+    ```CLI
     npm install
     ```
 1. Create a new folder using the command `mkdir <folder name>` inside the sample component folder and navigate into the folder using the command `cd <folder name>`. 
 1. Create a new solution project inside the folder using the following command:
-    ```
+    ```CLI
     pac solution init --publisher-name <Name of the publisher> --publisher-prefix <Publisher prefix>
     ```
 1. After the new solution project is created, refer to the ___location where the sample component is located. You can add the reference using the following command:
-    ```
+    ```CLI
     pac solution add-reference --path <Path to the root of the sample component>
     ```
 1. To generate a zip file from your solution project, you need to `cd` into your solution project directory and build the project using the following command:
-    ```msbuild /t:restore
+    
+     ```CLI
+     msbuild /t:restore
     ```
 1. Again, run the command `msbuild`.
 1. The generated solution zip file will be available at `Solution\bin\debug` folder. Manually [import the solution](/powerapps/maker/common-data-service/import-update-export-solutions) into your Common Data Service environment using the web portal once the zip file is ready. Alternatively, to import the solution using Power Apps CLI commands, see the [Connecting to your environment](https://docs.microsoft.com/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment) and [Deployment](https://docs.microsoft.com/powerapps/developer/component-framework/import-custom-controls#deploying-code-components) sections.