added banner to maker/common-data-service folder

Author: Buckley Guderian

powerapps-docs/maker/common-data-service/EnvironmentVariables.md

@@ -17,6 +17,8 @@ search.app:
 ---
 # Environment variables overview 
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 Apps and flows often require different configuration settings across environments. Environment variables as configurable input parameters allow management of data separately compared to hard-coding values within your customization or using additional tools. Because they're solution components, performance is much better than importing configuration data as record data.
 
 Benefits of using environment variables:

powerapps-docs/maker/common-data-service/actions.md

@@ -22,6 +22,8 @@ search.audienceType:
 # Use actions
 
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 Actions open a range of possibilities for composing business logic. With actions, you can perform operations, such as Create, Update, Delete, Assign, or Perform Action. Internally, an action creates a custom message. Developers refer to these actions as *messages*. Each of these messages is based on actions taken on an entity record. If the goal of a process is to create a record, then update it, and then assign it, there are three separate steps. Each step is defined by the capabilities of the entity—not necessarily your business process.  
 
 Actions provide the ability to define a single verb (or message) that matches an operation you need to perform for your business. These new messages are driven by a process or behavior rather than what can be done with an entity. These messages can correspond to verbs like Escalate, Convert, Schedule, Route, or Approve—whatever you need. The addition of these verbs helps provide a richer vocabulary for you to fluently define your business processes. You can apply this richer vocabulary from clients or integrations rather than having to write the action within clients. This also makes it easier because you can manage and log the success or failure of the entire action as a single unit.  

powerapps-docs/maker/common-data-service/api-limits-overview.md

@@ -17,6 +17,8 @@ search.app:
 ---
 # Common Data Service API limits overview
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 Common Data Service API limits help ensure service levels, availability and quality. Common Data Service API limits are part of the Power Platform Request limits and allocations. This topic will introduce limits specifically for Common Data Service applicable for Power Apps, Power Automate, and customer engagement apps (Dynamics 365 Sales, Dynamics 365 Customer Service, Dynamics 365 Field Service, Dynamics 365 Marketing, and Dynamics 365 Project Service Automation) connecting to Common Data Service. 
 
 For information about limits for all areas within Power Platform, see [Power Platform Request limits and allocations](/power-platform/admin/api-request-limits-allocations).

powerapps-docs/maker/common-data-service/autonumber-fields.md

@@ -25,6 +25,8 @@ search.app:
 ---
 # Autonumber fields
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 Autonumber fields are fields that automatically generate alphanumeric strings whenever they are created. Makers can customize the format of these fields to their liking, and then rely on the system to generate matching values that automatically fill them in at runtime.
 
 While autonumber fields are formally just text fields with additional functionality built on top of them, [Power Apps](https://make.powerapps.com/?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc) simplifies this concept by simply exposing **Autonumber** as a distinct data type under the **Text** category. It is important to note that the classic solution explorer doesn't support creating or managing autonumber fields.

powerapps-docs/maker/common-data-service/behavior-format-date-time-field.md

@@ -24,6 +24,8 @@ search.app:
 ---
 # Behavior and format of the Date and Time field
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 In Common Data Service, the Date and Time data type is used in many standard entity fields. Depending on what kind of date the field represents, you can choose different field behaviors: **User Local**, **Date Only** or **Time-Zone Independent**.  
 
 <a name="Behavior"></a>   

powerapps-docs/maker/common-data-service/best-practices-workflow-processes.md

@@ -26,6 +26,8 @@ search.audienceType:
 # Best practices for real-time workflow processes
 
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 This topic contains best practices for creating and managing real-time workflow processes.  
 
 

powerapps-docs/maker/common-data-service/cds-processes.md

@@ -24,6 +24,8 @@ search.app:
   - D365CE
 ---
 # Apply business logic in Common Data Service
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 There are several choices available for applying business logic in Common Data Service. 
 
 ## Business rules

powerapps-docs/maker/common-data-service/change-color-scheme-add-logo-match-organizations-brand.md

@@ -23,6 +23,8 @@ search.app:
 ---
 # Create a theme
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 You can create a custom look and feel (a theme), for your app by making changes to the default colors and visual elements provided in the uncustomized system. For example, you can create your personal product branding by adding a company logo and providing entity-specific coloring. A theme is created by using the customization tools in the user interface, without requiring a developer to write code. You can create, change or delete themes that are used in your organization. The theme customization is supported in the Web forms in Dynamics 365 for Outlook. You can define multiple themes, but only one can be set and published as the default theme.  
 
 <a name="UseThemes"></a>   

powerapps-docs/maker/common-data-service/change-solution-publisher-prefix.md

@@ -24,6 +24,8 @@ search.app:
 
 # Solution publisher overview
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 Every app you create or customization you make is part of a solution. Every solution has a publisher. You specify the publisher when you create a solution. 
 
 The solution publisher indicates who developed the app. For this reason, you should create a solution publisher that is meaningful. You can view the solution publisher for a solution by selecting **Settings** from the **Solutions** area in Power Apps.

powerapps-docs/maker/common-data-service/common-issues-resolutions-solution-checker.md

@@ -21,6 +21,8 @@ search.app:
 ---
 # Common issues and resolutions for solution checker
 
+[!INCLUDE[cc-data-platform-banner](../../includes/cc-data-platform-banner.md)]
+
 This article lists some common issues that you might encounter while using solution checker. Where applicable, workarounds are provided.
 
 ## You're unable to use solution checker to run analysis or download results