Updates for the September release

Author: jansenbe

docs/transform/modernize-userinterface-site-pages-dotnet.md

@@ -1,7 +1,7 @@
 ---
 title: Transform classic pages to modern client-side pages using .NET
 description: Explains how to transform classic wiki and web part pages into modern client side pages using the SharePoint .NET
-ms.date: 06/24/2019
+ms.date: 09/03/2019
 ms.prod: sharepoint
 localization_priority: Normal
 ---
@@ -205,7 +205,7 @@ using (var cc = new ClientContext(siteUrl))
 ```
 
 > [!NOTE]
-> - This feature is still in preview in the June 2019 release...it should support SharePoint 2013, 2016 and 2019
+> - This feature supports SharePoint 2010, 2013, 2016 and 2019 as source. Target is always SharePoint Online
 > - It's important to run your code on a machine that is able to connect to both the on-premises SharePoint server as the SharePoint Online environment
 > - There (currently) is no user mapping feature, hence item level permissions are not copied over from the on-premises publishing page to the SharePoint Online modern page
 > - This approach can also be used for page transformation across tenants (whenever that would make sense)

docs/transform/modernize-userinterface-site-pages-model-publishing.md

@@ -1,7 +1,7 @@
 ---
 title: Understanding and configuring the publishing page transformation model
 description: Provides detailed guidance on how to configure and use the publishing page transformation model
-ms.date: 06/26/2019
+ms.date: 09/03/2019
 ms.prod: sharepoint
 localization_priority: Normal
 ---
@@ -82,7 +82,7 @@ Upcoming chapters will provide more details.
 Let's analyze how a page layout mapping is configured in the page layout mapping model, which is best done based upon a sample definition:
 
 ```Xml
-    <PageLayout Name="MyPageLayout" AssociatedContentType="CustomPage1" PageLayoutTemplate="AutoDetect" PageHeader="Custom">
+    <PageLayout Name="MyPageLayout" AlsoAppliesTo="MyOtherPageLayout;MyOtherPageLayout2" AssociatedContentType="CustomPage1" PageLayoutTemplate="AutoDetect" PageHeader="Custom">
       <Header Type="FullWidthImage" Alignment="Left" ShowPublishedDate="true">
         <Field Name="PublishingRollupImage;PublishingPageImage" HeaderProperty="ImageServerRelativeUrl" Functions="ToImageUrl({@name})" />
         <Field Name="ArticleByLine" HeaderProperty="TopicHeader" Functions=""/>
@@ -128,10 +128,14 @@ Let's analyze how a page layout mapping is configured in the page layout mapping
 The following properties are used on the PageLayout element:
 
 - **Name**: contains the name of your page layout.
+- **AlsoAppliesTo**: when this mapping will be used for multiple page layouts then you can specify the names of those additional page layouts as a semi colon delimited list in this attribute. The **Name** property will be name of the first page layout, the **AlsoAppliesTo** just contains the additional ones.
 - **AssociatedContentType**: the name of the modern site page content type you want use. Leave this blank if you want to use the default site page content type.
 - **PageLayoutTemplate**: the layout system to use...defaults to `AutoDetect` which should work fine in all cases, but optionally you can pick a specific wiki layout as well.
 - **PageHeader**: controls the type of page header that will be used. Defaults to `Custom` as that allows for a nice header, but you can switch it to `None` for no header or `Default` for the default modern page header.
 
+> [!Note]
+> - The **AlsoAppliesTo** attribute  was introduced in the September 2019 release
+
 ### Header element
 
 The following properties are used on the Header element:
@@ -321,13 +325,14 @@ Now that the assembly has been defined you can use your functions and selectors
 
 ## Page layout mapping FAQ
 
-### I want to keep the source page creation and modification information
+### I want to keep the source page creation information (as of September 2019 release)
 
 You can do this by altering your page layout mapping like shown in below sample:
 
 ```XML
 <MetaData>
   ...
+  <!-- Use below 4 fields to retain user created/date created, user modified/date modified will be overwritten afterwards, but you need to include them to make this "override" work -->
   <Field Name="Created" TargetFieldName="Created" Functions="" />
   <Field Name="Modified" TargetFieldName="Modified" Functions="" />
   <Field Name="Author" TargetFieldName="Author" Functions="" />
@@ -336,17 +341,18 @@ You can do this by altering your page layout mapping like shown in below sample:
 </MetaData>
 ```
 
-If you however publish this page the modification data will change again. If you want to keep the modification date and publish you can add these 2 additional fields:
+On publishing this page the modification data will change again. If you want to keep the modification date shown correctly in the modern page header you should set this field as well:
 
 ```XML
 <MetaData>
   ...
-  <Field Name="PublishingStartDate" TargetFieldName="FirstPublishedDate" Functions="" />
-  <Field Name="ID" TargetFieldName="PromotedState" Functions="StaticString('2')" />
+  <Field Name="Modified" TargetFieldName="FirstPublishedDate" Functions=""/>
   ...
 </MetaData>
 ```
 
+In above sample the page modification date is taken as FirstPublishedDate, but you can also take other DateTime fields like ArticleStartDate.
+
 ### I want to promote the created pages as news
 
 Promoting pages created from a page layout as news pages can be be done by adding the below fields to your page layout mapping: