Merge pull request #327 from SKjerland/WN18041

[PowerApps] Added items to What's New and Common Issues for Train 18042; updated CDS naming; updated titles and metadata per MVC guidelines"

Author: GitHubber17

powerapps-docs/administrator/index.md

@@ -16,15 +16,16 @@ ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 03/21/2018
 ms.author: sharik
+#Customer intent: As a PowerApps administrator, I want to understand the PowerApps adoption journey so I can plan how to effectively protect my organization's data, manage users and data, monitor usage, deploy solutions, orchestrate updates, and identify and fix issues.
 
 ---
 
-# Administer PowerApps overview
-Administration of PowerApps, Microsoft Flow, and the Common Data Service is done through the [PowerApps Admin center]([https://admin.powerapps.com).
+# What's the role of a PowerApps administrator?
+Administration of PowerApps, Microsoft Flow, and Common Data Service for Apps is done through the [PowerApps Admin center]([https://admin.powerapps.com).
 
 ![](./media/index/admin-center.png)
 
-The evolution of an organization adopting PowerApps, Microsoft Flow, and the Common Data Service starts with the administrator. As an administrator, you begin your journey asking how you can protect your organization's data. What data is accessible through these services? Are there best practices you can follow? You'll need to understand the PowerApps security model and decide how you're going to control access to data. Once you have a handle on all of this, you'll then want to know how you can monitor and manage what users are doing with these services.
+The evolution of an organization adopting PowerApps, Microsoft Flow, and CDS for Apps starts with the administrator. As an administrator, you begin your journey asking how you can protect your organization's data. What data is accessible through these services? Are there best practices you can follow? You'll need to understand the PowerApps security model and decide how you're going to control access to data. Once you have a handle on all of this, you'll then want to know how you can monitor and manage what users are doing with these services.
 
 When you have control and visibility figured out, the next part of your journey takes you to deployment. Individual users and teams can deploy apps on their own, but how do you centrally deploy solutions for your entire organization? And how do you orchestrate updates and identify and fix issues?
 

powerapps-docs/maker/canvas-apps/common-issues-and-resolutions.md

@@ -14,12 +14,16 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 03/05/2018
+ms.date: 04/09/2018
 ms.author: sharik
 
 ---
 # Common issues and resolutions for PowerApps
 ## Recently added/changed
+1. **Copying and pasting screens across apps**
+
+	Copying and pasting screens across apps is not currently supported. To work around this, add a new screen to your target app, copy the controls from the screen in your source app, and then paste them into the screen of your target app. 
+
 1. **Changing the layout of SharePoint forms**
 
 	While customizing a SharePoint list form in certain languages, if you try to change the layout from portrait (default) to landscape, the app may show multiple errors (yellow triangles in controls). To resolve these errors and retain the landscape layout, click **Undo**.

powerapps-docs/maker/canvas-apps/release-notes.md

@@ -14,7 +14,7 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 03/21/2018
+ms.date: 04/09/2018
 ms.author: sharik
 
 ---
@@ -31,18 +31,20 @@ Discover the latest updates to our business applications, as well as a host of n
 
 **Coming soon:** We'll keep updating the release notes PDF as features ship, and we'll also make them available on a web page.
 
-## Mar. 21
-1. Create [model-driven apps](../model-driven-apps/model-driven-app-overview.md), which start with your data model and build up from the shape of your core business data and processes in the Common Data Service to model forms, views, and other components. Model-driven apps automatically generate great UI that is responsive across devices.
-2. [Create a database](../../administrator/create-database.md) on the latest version of the Common Data Service in an environment.
-3. The Common Data Service for Apps now includes:
+## Apr. 9
+* Cut (Ctrl+X), copy (Ctrl+C), and paste (Ctrl+V) controls—including the controls' styles, formulas, and properties—across apps in a web browser.
 
+## Mar. 21
+1. Create [model-driven apps](../model-driven-apps/model-driven-app-overview.md), which start with your data model and build up from the shape of your core business data and processes in Common Data Service for Apps to model forms, views, and other components. Model-driven apps automatically generate great UI that is responsive across devices.
+2. [Create a database](../../administrator/create-database.md) on the latest version of CDS for Apps in an environment.
+3. CDS for Apps now includes:
     - **Additional data types** support more complex entity definitions and provide richer experiences. (Applies to canvas and model-driven apps.)
-    - [Create and customize entities](../common-data-service/data-platform-create-entity.md) in the Common Data Service for Apps right from the PowerApps site. The **refreshed experience** includes improved performance, a more user-friendly UI, and helpful features such as in-line creation of option sets. (Applies to canvas and model-driven apps.)
-    - Create **server-side business rules** for validating data entered into the Common Data Service for Apps. (Applies to canvas and model-driven apps.)
-    - Create **calculated and rollup fields** in Common Data Service for Apps entities directly from the PowerApps site. (Applies to canvas and model-driven apps.)  
-    - Developers can use the Common Data Service for Apps **Software Development Kit** (SDK) to create code-based customizations for the Common Data Service.
-    - Advanced users can access data stored in the Common Data Service for Apps through a new **OData Web API**.
-    - [Import data](../common-data-service/data-platform-cds-newentity-pq.md) into Common Data Service with **Power Query**. Use Power Query on the web to directly import data to the Common Data Service for Apps from multiple sources
+    - [Create and customize entities](../common-data-service/data-platform-create-entity.md) in CDS for Apps right from the PowerApps site. The **refreshed experience** includes improved performance, a more user-friendly UI, and helpful features such as in-line creation of option sets. (Applies to canvas and model-driven apps.)
+    - Create **server-side business rules** for validating data entered into CDS for Apps. (Applies to canvas and model-driven apps.)
+    - Create **calculated and rollup fields** in CDS for Apps entities directly from the PowerApps site. (Applies to canvas and model-driven apps.)  
+    - Developers can use the CDS for Apps **Software Development Kit** (SDK) to create code-based customizations for CDS for Apps.
+    - Advanced users can access data stored in CDS for Apps through a new **OData Web API**.
+    - [Import data](../common-data-service/data-platform-cds-newentity-pq.md) into CDS for Apps with **Power Query**. Use Power Query on the web to directly import data to CDS for Apps from multiple sources
 
 ## Mar. 5
 1. Add (and delete) [attachments](controls/control-attachments.md) to SharePoint lists.
@@ -80,8 +82,3 @@ Discover the latest updates to our business applications, as well as a host of n
 
 ## Nov. 10
 * [Rename rules](working-with-rules.md) in an app and show rules when the selected control is in the rule condition.
-
-## Oct. 30
-1. [Show all rules](working-with-rules.md) in an app, not just those for the selected control.
-2. Add icons that app creators requested the most.
-3. Improved performance of apps on Android and iOS devices.

powerapps-docs/maker/common-data-service/data-platform-intro.md

@@ -1,6 +1,6 @@
 ---
-title: Common Data Service for Apps | Microsoft Docs
-description: Introduction to the Common Data Service for Apps, Entities and Server side logic.
+title: What is Common Data Service for Apps? | Microsoft Docs
+description: Introduction to Common Data Service for Apps, entities, and server-side logic.
 services: powerapps
 documentationcenter: na
 author: clwesene
@@ -10,35 +10,35 @@ tags: ''
 
 ms.service: powerapps
 ms.devlang: na
-ms.topic: article
+ms.topic: overview
 ms.tgt_pltfrm: na
 ms.workload: na
 ms.date: 3/21/2018
 ms.author: clwesene
 
 ---
-# Common Data Service for Apps
+# What is Common Data Service for Apps?
 
-The Common Data Service allows you to securely store and manage data which is used in apps you've developed or apps from Microsoft and app providers. Data within the Common Data Service is stored within a set of standard and custom entities. An entity is a set of fields used to store data similarly to a table within a database. After your data is stored you can use Microsoft PowerApps to build rich applications using your data:
+Common Data Service for Apps allows you to securely store and manage data that's used in apps you've developed or apps from Microsoft and app providers. Data within CDS for Apps is stored within a set of standard and custom entities. An entity is a set of fields used to store data similarly to a table within a database. After your data is stored you can use Microsoft PowerApps to build rich applications using your data:
 
 * Leverage existing standard entities or create custom entities to support your scenario and application.
-* Create PowerApps and Flows directly against the Common Data Service.
+* Create PowerApps and Flows directly against CDS for Apps.
 * Add custom fields, and relationships to standard entities where additional information is needed.
 * Create calculated and roll up fields to your entities to provide consistent calculations across apps and analytics.
 * Define business rules to ensure data quality within entities, regardless of the which app is accessing or editing your data.
 * Create workflows and leverage integration with Microsoft Flow to drive additional actions and business processes against your data.
 * Incorporate standard and custom entities into an app that you're developing as easily as you would with data in other sources.
-* Connect to your data from Microsoft Excel using the Common Data Service productivity add-ins.
+* Connect to your data from Microsoft Excel using CDS for Apps productivity add-ins.
 * Easily import and synchronize your data using Power Query.
 * Secure your data within your organization using role-based security against standard and custom entities.
 * Provide global support for your data and applications by leveraging translation of entity and field names in your user's language.
 
 Each entity contains a set of records that users can create, read, update, and delete depending on their permissions. You can create relationships between entities so that you can look up information in one entity based on a record in another entity. For example, you could create a custom entity to track events which a customer had attended. By adding the Customer to your custom entity as a lookup field, you establish a relationship between the two entities which can be leveraged in your app and in reporting.
 
-For information on purchasing a plan for using the Common Data Service, see [Pricing info](../../administrator/pricing-billing-skus.md).
+For information on purchasing a plan for using CDS for Apps, see [Pricing info](../../administrator/pricing-billing-skus.md).
 
-## Why use the Common Data Service for Apps?
-Entities within the Common Data Service, both standard and custom, allow a secure and cloud-based storage option for your data. Entities allow you to create a business-focused definition of your data for use within your apps. If you're not sure if entities are your best option, consider these benefits:
+## Why use Common Data Service for Apps?
+Entities within CDS for Apps, both standard and custom, allow a secure and cloud-based storage option for your data. Entities allow you to create a business-focused definition of your data for use within your apps. If you're not sure if entities are your best option, consider these benefits:
 
 * **Easy to manage** - Both the metadata and data are stored in the cloud. You don't need to worry about the details of how they're stored.
 * **Easy to share** - You can easily share data with your colleagues because PowerApps manages the permissions.
@@ -49,7 +49,7 @@ Entities within the Common Data Service, both standard and custom, allow a secur
 
 When you develop an app, you can use standard entities, custom entities, or both. If a standard entity can serve a particular purpose in your app, you should use it rather than developing a custom entity that does the same thing. If a standard entity would serve a purpose with a few changes, you can add fields to suit your needs.
 
-* The Common Data Service provides standard entities by default. These are designed, in accordance with best practices, to capture the most common concepts for an organization, such as Contacts, Accounts, and Products. For a full list of entities, see [Standard entities](data-platform-intro.md#standard-entities).
+* CDS for Apps provides standard entities by default. These are designed, in accordance with best practices, to capture the most common concepts for an organization, such as Contacts, Accounts, and Products. For a full list of entities, see [Standard entities](data-platform-intro.md#standard-entities).
 * You can extend the functionality of standard entities by creating one or more custom entities to store information that's unique to your organization. For more information, see [How to create a custom entity](create-custom-entity.md).
 
 > [!NOTE]
@@ -66,34 +66,33 @@ When using a standard entity or creating a custom entity there are multiple elem
 * Each entity can have multiple **relationships** to other entities to support look ups and queries across entities. Relationships can create to support Many-to-one, One-to-many and Many-to-many relationships.
 * **Views** allow each entity can be presented in multiple ways, including which fields are displayed, filtering and sorting of the data. These presentations are saved as views and can be consumed in different apps, for example you may only want to see Active Accounts within your app so you would use a view which is pre filtered to only show Active accounts to avoid repeating the filter in each consuming app.
 * **Business rules**  can be used to validate data being created and updated in entities to ensure data quality. Each business rule can validate data across multiple fields and entities, prompt warning and error messages regardless of the app being used to create the data.
-* **Data** stored within the Common Data Service is available through the PowerApps portal, PowerApps, Microsoft Excel and Web APIs for Developers.
+* **Data** stored within CDS for Apps is available through the PowerApps portal, PowerApps, Microsoft Excel and Web APIs for Developers.
 
 ### System fields
 All entities, whether standard or custom, are created with a set of read-only fields that you can't change, delete, or set to a value. These are the most important system fields:
 
 ## Logic and validation
 
-Entities within the Common Data Service can leverage rich server-side logic and validation to ensure data quality and reduce repetitive code in each app creating and using data in the entity.
+Entities within CDS for Apps can leverage rich server-side logic and validation to ensure data quality and reduce repetitive code in each app creating and using data in the entity.
 
 * **Business rules** can validate data across multiple fields and entities, prompt warning and error messages regardless of the app being used to create the data. For more information, see [Create a business rule](./data-platform-create-business-rule.md).
 * **Business process flows** guide users to ensure data is entered consistently and follow the same steps every time. Business process flows are currently only supported for Model driven apps. For more information, see [Business process flows overview](/dynamics365/customer-engagement/customize/business-process-flows-overview).
 * **Workflows** allow you to automate business processes without a user interaction. For more information, see [Workflows overview](/dynamics365/customer-engagement/customize/workflow-processes).
 * **Business logic with code** supports more advanced developer scenarios to extend there application directly through code. For more information, see [Apply business logic with code](../../developer/common-data-service/apply-business-logic-with-code.md).
 
-## Getting Data into the Common Data Service
+## Getting Data into Common Data Service for Apps
 
-There are several ways to start getting data into the Common Data Service:
+There are several ways to start getting data into CDS for Apps:
 
 * Create a PowerApp or Flow to start creating data.
-* Use Power Query to connect to an online or on-premise data source and import it directly into the Common Data Service. Power Query also allows you to create the entities during import based off the schema of your source as well as perform transformations to your data during import. For more information, see [Add data to an entity in the Common Data Service by using Power Query](./data-platform-cds-newentity-pq.md).
+* Use Power Query to connect to an online or on-premise data source and import it directly into CDS for Apps. Power Query also allows you to create the entities during import based off the schema of your source as well as perform transformations to your data during import. For more information, see [Add data to an entity in Common Data Service for Apps by using Power Query](./data-platform-cds-newentity-pq.md).
 
 ## Developer Capabilities
 
-In addition to the features available through the [PowerApps](https://web.powerapps.com) portal, the Common Data Service also includes features for developers to programmatically access metadata and data to create entities and business logic, as well as interact with data. For more information, see [Common Data Service for Apps Developer Overview](../../developer/common-data-service/overview.md)
+In addition to the features available through the [PowerApps](https://web.powerapps.com) portal, CDS for Apps also includes features for developers to programmatically access metadata and data to create entities and business logic, as well as interact with data. For more information, see [Common Data Service for Apps Developer Overview](../../developer/common-data-service/overview.md)
 
 ## Get started
 Try it out by creating an app using a standard entity or [create a custom entity](create-custom-entity.md), and then [create an app that uses that entity](../canvas-apps/data-platform-create-app.md).
 
 ## Privacy notice
 With the Microsoft PowerApps common data model we collect and store custom entity and field names in our diagnostic systems.  We use this knowledge to improve the common data model for our customers. The entity and field names that Creators create help us understand scenarios that are common across the Microsoft PowerApps community and ascertain gaps in the service’s standard entity coverage, such as schemas related to organizations. The data in the database tables associated with these entities is not accessed or used by Microsoft or replicated outside of the region in which the database is provisioned. Note, however, the custom entity and field names may be replicated across regions and are deleted in accordance with our data retention policies. Microsoft is committed to your privacy as described further in our [Trust Center](https://www.microsoft.com/trustcenter/Privacy/default.aspx).
-