Merge pull request #4400 from MicrosoftDocs/stjanovi-patch-7

Added limitation on offline support

Author: Mattp123

powerapps-docs/maker/data-platform/map-entity-fields.md

@@ -52,7 +52,9 @@ When you map table columns for a 1:N table relationship certain items of data fr
 > [!NOTE]
 > These mappings only set default values to a row before it is saved. People can edit the values before saving. The data that is transferred is the data at that point in time. It isn’t synchronized if the source data later changes.
 >   
-> These mappings aren’t applied to related rows created using a workflow or dialog process. They aren’t automatically applied to new rows created using code, although developers can use a special message called `InitializeFrom` ([InitializeFrom Function](/dynamics365/customer-engagement/web-api/initializefrom?view=dynamics-ce-odata-9) or [InitializeFromRequest Class](/dotnet/api/microsoft.crm.sdk.messages.initializefromrequest?view=dynamics-general-ce-9)) to create a new row using available mappings.  
+> These mappings aren’t applied to related rows created using a workflow or dialog process. They aren’t automatically applied to new rows created using code, although developers can use a special message called `InitializeFrom` ([InitializeFrom Function](/dynamics365/customer-engagement/web-api/initializefrom?view=dynamics-ce-odata-9) or [InitializeFromRequest Class](/dotnet/api/microsoft.crm.sdk.messages.initializefromrequest?view=dynamics-general-ce-9)) to create a new row using available mappings. 
+> 
+> These mappings aren't applied for new related table forms that are opened when an app is in offline mode, except for parent lookup fields. 
 
 ## Open solution explorer
 
@@ -123,4 +125,4 @@ Because column mappings are not metadata, you must publish them before changes t
 [Developer Documentation: Web API Create a new table from another table](/dynamics365/customer-engagement/developer/webapi/create-entity-web-api#create-a-new-table-from-another-table)
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]