SAP-docs
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7b50e8e.md
+5 b/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/add-a-source-7b50e8e.md
+5
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/running-a-flow-5b591d4.md
+3 b/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/running-a-flow-5b591d4.md
+3
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/using-an-object-without-primary-key-as-the-source-2267a9f.md
+22 b/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/using-an-object-without-primary-key-as-the-source-2267a9f.md
+22
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/using-confluent-kafka-as-the-target-74b3c95.md
+1-1 b/‎docs/Acquiring-Preparing-Modeling-Data/Acquiring-and-Preparing-Data-in-the-Data-Builder/using-confluent-kafka-as-the-target-74b3c95.md
+1-1
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/finding-and-accessing-data-in-the-catalog-1047825.md
+11 b/‎docs/Acquiring-Preparing-Modeling-Data/Creating-Finding-Sharing-Objects/finding-and-accessing-data-in-the-catalog-1047825.md
+11
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-dimension-4caf098.md
+1 b/‎docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-dimension-4caf098.md
+1
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-prefix-or-a-suffix-0373c60.md
+30 b/‎docs/Acquiring-Preparing-Modeling-Data/Modeling-Data-in-the-Data-Builder/add-a-prefix-or-a-suffix-0373c60.md
+30
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/index.md
+2 b/‎docs/Acquiring-Preparing-Modeling-Data/index.md
+2
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/searching-and-browsing-2dfea3a.md
+5 b/‎docs/Acquiring-Preparing-Modeling-Data/searching-and-browsing-2dfea3a.md
+5
diff --git a/‎docs/Acquiring-Preparing-Modeling-Data/viewing-object-data-b338e4a.md
+7-3 b/‎docs/Acquiring-Preparing-Modeling-Data/viewing-object-data-b338e4a.md
+7-3
diff --git a/‎docs/Administering/Creating-Spaces-and-Allocating-Storage/create-a-space-bbd41b8.md
+3-3 b/‎docs/Administering/Creating-Spaces-and-Allocating-Storage/create-a-space-bbd41b8.md
+3-3
diff --git a/‎docs/Administering/Managing-Users-and-Roles/creating-a-new-user-58d4b24.md renamed to ‎docs/Administering/Managing-Users-and-Roles/create-a-user-58d4b24.md
+1-1 b/‎docs/Administering/Managing-Users-and-Roles/creating-a-new-user-58d4b24.md renamed to ‎docs/Administering/Managing-Users-and-Roles/create-a-user-58d4b24.md
+1-1
diff --git a/‎docs/Administering/Managing-Users-and-Roles/deleting-users-3ceb94c.md renamed to ‎docs/Administering/Managing-Users-and-Roles/delete-users-3ceb94c.md
+4-4 b/‎docs/Administering/Managing-Users-and-Roles/deleting-users-3ceb94c.md renamed to ‎docs/Administering/Managing-Users-and-Roles/delete-users-3ceb94c.md
+4-4
diff --git a/‎docs/Administering/Managing-Users-and-Roles/enabling-a-custom-saml-identity-provider-9b26536.md
+1-1 b/‎docs/Administering/Managing-Users-and-Roles/enabling-a-custom-saml-identity-provider-9b26536.md
+1-1
diff --git a/‎docs/Administering/Managing-Users-and-Roles/exporting-users-e227d3c.md renamed to ‎docs/Administering/Managing-Users-and-Roles/export-users-e227d3c.md
+1-1 b/‎docs/Administering/Managing-Users-and-Roles/exporting-users-e227d3c.md renamed to ‎docs/Administering/Managing-Users-and-Roles/export-users-e227d3c.md
+1-1
diff --git a/‎docs/Administering/Managing-Users-and-Roles/importing-or-modifying-users-from-a-file-b2698da.md renamed to ‎docs/Administering/Managing-Users-and-Roles/import-or-modify-users-from-a-file-b2698da.md
+3-3 b/‎docs/Administering/Managing-Users-and-Roles/importing-or-modifying-users-from-a-file-b2698da.md renamed to ‎docs/Administering/Managing-Users-and-Roles/import-or-modify-users-from-a-file-b2698da.md
+3-3
@@ -71,6 +71,11 @@ Add a source to read data from. You can add multiple sources and combine them to
     <td valign="top">
 
     \[read-only\] Provide information to identify the source table.
+
+    > ### Note:  
+    > Business names are not supported for columns in data flow editor.
+
+
 
     </td>
     </tr>
 
@@ -12,6 +12,9 @@ To run a flow, you have 3 main options depending on your flow type:
 -   Click *Schedule* to run your data flow or your transformation flow at later time, or on regular basis \(this is not available for *Replication Flow*\).
 -   Add the flow into a task chain. This is only valid for a data flow. For more information, see [Creating a Task Chain](creating-a-task-chain-d1afbc2.md).
 
+> ### Caution:  
+> A data flow uses a technical user during run. So, if a source view or an underlying view of the source view uses the SESSION\_CONTEXT function, incorrect data is read from the view during the execution of the data flow. This results in incorrect data or no data in the output.
+
 
 
 <a name="loio5b591d4998fa4a148750016a29ada91e__section_kxy_dq3_pzb"/>
 
@@ -0,0 +1,22 @@
+<!-- loio2267a9f6a5724ec0ae5632db4f9f70e5 -->
+
+# Using an Object Without Primary Key As the Source
+
+If certain conditions are met, you can use objects that do not have a primary key as the source for a replication flow.
+
+This applies to the following types of **source objects**:
+
+-   CDS views
+
+-   ODP artifacts
+
+
+The objects must have load type *Initial Only*. \(Delta loading is not supported.\)
+
+**Existing tables** can be used as **targets** if they have a column \_\_load\_package\_id \(as explained below\). **Local tables** can only be used as targets if delta capturing is **not** enabled.
+
+For some targets, the system automatically adds a **technical target column**. For HANA and HANA Cloud targets, this column is called "\_\_load\_package\_id" and has data type binary\(\>=256\). For other targets, it is called "\_\_load\_record\_id" and has data type string\(44\). This column provides a unique identifier for each record, which serves as a replacement for the primary key in duplicate handling and for other technical purposes. On the Projections tab, this column is always shown at the end and in read only mode. You can't rename it, remove or modify its data type, or reorder it.
+
+> ### Note:  
+> Multiple replications \(for example due to restarting or undeploying and redeploying a replication flow\) result in different \_\_load\_record\_id values for the same source record.
+
@@ -171,7 +171,7 @@ For more information, see [Using Confluent Kafka As the Target](using-confluent-
 The **target container** is automatically set to "/" because Confluent Kafka does not have a superordinate container layer.
 
 > ### Note:  
-> If the Kafka cluster is behind an SAP Cloud Connector \(SCC\), the Kafka cluster and the SCC must be configured such that the broker addresses advertised by the cluster match the virtual hosts maintained for the brokers in the SCC. The simplest solution is to use the same value for virtual and internal hosts in the SCC and to maintain no dedicated advertised listeners for the Kafka brokers. If advertised listeners are maintained, these must be used as virtual hosts in SCC and as broker addresses in the connection definition.
+> If the Kafka cluster is behind an SAP Cloud Connector \(SCC\), the Kafka cluster and the SCC must be configured such that the broker addresses advertised by the cluster match the virtual hosts maintained for the brokers in the SCC. The simplest solution is to use the same value for virtual and internal hosts in the SCC and to maintain no dedicated advertised listeners for the Kafka brokers. When adding additional brokers to a cluster to scale up, the SCC mapping must be adapted to include the additional brokers.
 
 Each record from the source system is transferred into a single **message** in the target topic. The key of the messages is the combination of all primary key values of the record concatenated by "\_".
 
 
@@ -264,6 +264,17 @@ You can change the view to see different information.
 -   <span class="FPA-icons-V3"></span> \(Display as List\)
 -   <span class="SAP-icons-V5"></span> \(Display as Table\)
 
+
+
+<a name="loio10478251045b43e782fa15e0f3e113b0__section_vcp_wg5_zbc"/>
+
+## Search for Third-Party Data
+
+You can use the Datarade Data Finder website to search and request additional third-party data products from various data providers. Access the Datarade website from the catalog by choosing the *Data Products* tab or the *Data Providers* tab, and then clicking the *Request Data from Datarade* button.
+
+> ### Note:  
+> Clicking the *Request Data from Datarade* button takes you to the Datarade website. This site is external to our product.
+
 **Related Information**  
 
 
 
@@ -46,5 +46,6 @@ There are different ways to add dimensions:
     -   You can change the alias of this item in the properties panel. The alias is the name that is shown in the story in SAP Analytics Cloud.
     -   You can add or deselect associated dimensions.
     -   You can add or deselect attributes.
+    -   You can specify a custom prefix or suffix for the technical name of attributes. For more information, see [Add a Prefix or a Suffix](add-a-prefix-or-a-suffix-0373c60.md).
 
 
@@ -0,0 +1,30 @@
+<!-- loio0373c60d7e614dd5b5189de767bb672b -->
+
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
+# Add a Prefix or a Suffix
+
+You can specify a custom prefix or suffix for the technical name of attributes.
+
+
+
+## Context
+
+The suffix/prefix is a dimension property that is added to all attributes of that dimension. This helps you to identify where an attribute originates from when your analytic model contains a dimension multiple times, as the attribute name is be taken from the source dimension and would be the same in each dimension.
+
+> ### Example:  
+> An analytic model contains the dimension *Employee* three times, as *Product Manager*, *Responsible* and *Changed By*. You can add the prefix PM for *Employee* in *Product Manager*, the prefix RESP for *Employee* in *Responsible*, and CB for the *Employee* in *Changed By*.
+
+
+
+## Procedure
+
+1.  Click on a dimension of the canvas to show its properties in the side panel.
+
+2.  Choose <span class="FPA-icons-V3"></span> Edit to edit the prefix or suffix for the technical name of attributes. Note that prefixes cannot start with an underscore.
+
+3.  You can reset the technical names of attributes.
+
+    When you select *Reset all attributes to the original source names*, you can reset the technical names. When an attribute's technical name is renamed with a counter because of conflicts, this function removes that counter by resetting the technical name to match the source. This does not affect prefixes and suffixes.
+
+
@@ -80,6 +80,7 @@
         -   [Configure Your Replication Flow](Acquiring-and-Preparing-Data-in-the-Data-Builder/configure-your-replication-flow-3f5ba0c.md)
         -   [Define Filters](Acquiring-and-Preparing-Data-in-the-Data-Builder/define-filters-5a6ef36.md)
         -   [Define Mapping](Acquiring-and-Preparing-Data-in-the-Data-Builder/define-mapping-2c7948f.md)
+        -   [Using an Object Without Primary Key As the Source](Acquiring-and-Preparing-Data-in-the-Data-Builder/using-an-object-without-primary-key-as-the-source-2267a9f.md)
         -   [Using a Cloud Storage Provider As the Target](Acquiring-and-Preparing-Data-in-the-Data-Builder/using-a-cloud-storage-provider-as-the-target-43d93a2.md)
         -   [Using Google BigQuery As the Target](Acquiring-and-Preparing-Data-in-the-Data-Builder/using-google-bigquery-as-the-target-56d4472.md)
         -   [Using Apache Kafka As the Target](Acquiring-and-Preparing-Data-in-the-Data-Builder/using-apache-kafka-as-the-target-6df55db.md)
@@ -175,6 +176,7 @@
         -   [Create an Analytic Model Directly From a View or Table](Modeling-Data-in-the-Data-Builder/create-an-analytic-model-directly-from-a-view-or-table-1c674aa.md)
         -   [Add a Source](Modeling-Data-in-the-Data-Builder/add-a-source-27075ee.md)
         -   [Add a Dimension](Modeling-Data-in-the-Data-Builder/add-a-dimension-4caf098.md)
+            -   [Add a Prefix or a Suffix](Modeling-Data-in-the-Data-Builder/add-a-prefix-or-a-suffix-0373c60.md)
         -   [Add Measures](Modeling-Data-in-the-Data-Builder/add-measures-e4cc3e8.md)
             -   [Create a Calculated Measure](Modeling-Data-in-the-Data-Builder/create-a-calculated-measure-cf6bd08.md)
             -   [Create a Restricted Measure](Modeling-Data-in-the-Data-Builder/create-a-restricted-measure-bfb43dd.md)
 
@@ -18,3 +18,8 @@ For more information on the available filters, see [Overview of Filters](overvie
 
 By clicking an entry in the search result list, you will be directly forwarded to the corresponding data product page or data provider profile. There, you can evaluate the data product or data provider and eventually bookmark them. For more information, see [Using Bookmarks](using-bookmarks-aec68bb.md).
 
+You can use the Datarade data finder website to search and request additional third-party data products from various data providers. Access Datarade by clicking the *Request Data from Datarade* button.
+
+> ### Note:  
+> Clicking the *Request Data from Datarade* button takes you to the Datarade website. This site is external to our product.
+
@@ -43,8 +43,6 @@ You can view data in the table, graphical view, SQL view, E/R model, analytic mo
     > -   The *Data Viewer* will time out and display an error on the *Errors* tab if it is unable to load data in under three minutes. If you experience timeouts or slow performance and some or all of the data you want to view is not replicated to SAP Datasphere, consider replicating it \(see [Replicate Remote Table Data](Acquiring-and-Preparing-Data-in-the-Data-Builder/replicate-remote-table-data-7e258a7.md)\).
     > -   If a column has a *HANA Numeric* data type its data cannot be shown. Consider, changing the data type to one supported by SAP Datasphere \(see [Column Data Types](Acquiring-and-Preparing-Data-in-the-Data-Builder/column-data-types-7b1dc6e.md)\).
     > -   If a column has *Binary*, *Large Binary*, *ST\_Point*, and *ST\_Geometry* set as data type, the data viewer is unavailable and records are shown as *Cannot be shown*. If no data can be found, the data viewer shows it as *NULL*.
-    > -   You cannot view data in an SQL view if any of its sources is shared from another space and has an input parameter.
-    > 
     > -   When viewing data in a persisted view, the data is read from the view's persistency table, unless the view has a status of *Changes to Deploy*, in which case the view is run and the results displayed.
 
 4.  The following tools are available in the panel toolbar:
@@ -218,8 +216,14 @@ You can review the effects of any data access controls you apply to a view by ch
     The data viewer updates to show only the records visible to the selected user.
 
     > ### Note:  
-    > *View as User* is only available in the graphic view, SQL view, and analytic model editors, and can only simulate data access controls that are applied in the current space and have a status of *Deployed*. If your view has one or more sources shared from other spaces, then a warning is shown to indicate that you may not see exactly the same records as the user you are impersonating.
+    > *View as User* is only available in the graphic view, SQL view, and analytic model editors, and can only simulate data access controls that are applied in the current space and which have a status of *Deployed*. In addition, if the view:
+    > 
+    > -   Is shared from another space then *View as User* is not supported.
+    > -   Has one or more sources shared from other spaces, then a warning is shown to indicate that you may not see exactly the same records as the user you are impersonating.
+    > -   Is secured by data access controls created by importing analysis authorizations from SAP BW or SAP BW/4HANA, then *View as User* is not supported.
+
 
+For more information about data access controls, see [Securing Data with Data Access Controls](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/a032e51c730147c7a1fcac125b4cfe14.html "Data access controls allow you to apply row-level security to your objects. When a data access control is applied to a data layer view or a business layer object, any user viewing its data will see only the rows for which they are authorized, based on the specified criteria.") :arrow_upper_right:.
 
 
 
 
@@ -243,7 +243,7 @@ Create a space, allocate storage, and set the space priority and statement limit
         > ### Note:  
         > A user with the DW Administrator role only cannot see the *Time Tables and Dimensions* area.
 
-    -   *Auditing*/*Space Audit Settings* - Use the properties in the *Space Audit Settings* section to enable audit logging for the space. See [Enable Audit Logging](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/266553976e1c4db9aaa28a75e2308b77.html "You can enable audit logs for your space so that read and change actions (policies) are recorded. Administrators can then analyze who did what and when in the database.") :arrow_upper_right:.
+    -   *Auditing*/*Space Audit Settings* - Use the properties in the *Space Audit Settings* section to enable audit logging for the space. See [Enable Audit Logging](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/266553976e1c4db9aaa28a75e2308b77.html "You can enable audit logs for your space so that read and change actions (policies) are recorded. Administrators can then analyze who performed which action at which point in time.") :arrow_upper_right:.
 
 7.  Click *Deploy* to deploy your space to the database.
 
@@ -252,8 +252,8 @@ Create a space, allocate storage, and set the space priority and statement limit
     -   Add your space to an existing scoped role \(see [Add Spaces to a Scoped Role](../Managing-Users-and-Roles/create-a-scoped-role-to-assign-privileges-to-users-in-spaces-b5c4e0b.md#loiob5c4e0b6c462414783ebbfc053815521__section_pr1_5pj_zyb)\).
     -   Create a scoped role and add your space and at least one user to the scoped role \(see [Create a Scoped Role](../Managing-Users-and-Roles/create-a-scoped-role-to-assign-privileges-to-users-in-spaces-b5c4e0b.md#loiob5c4e0b6c462414783ebbfc053815521__section_z4m_mpj_zyb)\).
 
-    For more information, see [Create a Scoped Role to Assign Privileges to Users in Spaces](../Managing-Users-and-Roles/create-a-scoped-role-to-assign-privileges-to-users-in-spaces-b5c4e0b.md)\).
+    For more information, see [Create a Scoped Role to Assign Privileges to Users in Spaces](../Managing-Users-and-Roles/create-a-scoped-role-to-assign-privileges-to-users-in-spaces-b5c4e0b.md).
 
-    All users assigned to the space via the scoped roles are automatically displayed in the *Users* area of the space page. In this area, you can add or remove users to/from scoped roles for your space \(see [Control User Access to Your Space](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/9d59fe511ae644d98384897443054c16.html "You can assign users to your space and manage them.") :arrow_upper_right:. Either an administrator or a user with space administrator privileges can do so.
+    All users assigned to the space via the scoped roles are automatically displayed in the *Users* area of the space page. In this area, you can add or remove users to/from scoped roles for your space \(see [Control User Access to Your Space](https://help.sap.com/viewer/9f36ca35bc6145e4acdef6b4d852d560/DEV_CURRENT/en-US/9d59fe511ae644d98384897443054c16.html "You can assign users to your space and manage them.") :arrow_upper_right:\). Either an administrator or a user with space administrator privileges can do so.
 
 
@@ -2,7 +2,7 @@
 
 <link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
 
-# Creating a New User
+# Create a User
 
 You can create individual users in SAP Datasphere.
 
 
@@ -2,7 +2,7 @@
 
 <link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
 
-# Deleting Users
+# Delete Users
 
 You can delete users.
 
@@ -24,9 +24,9 @@ You can delete users.
 **Related Information**  
 
 
-[Creating a New User](creating-a-new-user-58d4b24.md "You can create individual users in SAP Datasphere.")
+[Create a User](create-a-user-58d4b24.md "You can create individual users in SAP Datasphere.")
 
-[Importing or Modifying Users from a File](importing-or-modifying-users-from-a-file-b2698da.md "You can create new users or batch-update existing users by importing user data that you have saved in a CSV file.")
+[Import or Modify Users from a File](import-or-modify-users-from-a-file-b2698da.md "You can create users or batch-update existing users by importing user data that you have saved in a CSV file.")
 
-[Updating User Email Addresses](updating-user-email-addresses-0889208.md "You can update the user email addresses used for logon.")
+[Update User Email Addresses](update-user-email-addresses-0889208.md "You can update the user email addresses used for logon.")
 
@@ -303,7 +303,7 @@ SAP Datasphere can be hosted on non-SAP data centers.
     When dynamic user creation is enabled, new users will be automatically created using the default role and will be able to use SAML SSO to log onto SAP Datasphere. After users are created, you can set roles using SAML attributes.
 
     > ### Note:  
-    > Automatic user deletion is not supported. If a user in SAP Datasphere is removed from your SAML IdP, you must go to *Security* \> *Users* and manually delete users. For more information, see [Deleting Users](deleting-users-3ceb94c.md).
+    > Automatic user deletion is not supported. If a user in SAP Datasphere is removed from your SAML IdP, you must go to *Security* \> *Users* and manually delete users. For more information, see [Delete Users](delete-users-3ceb94c.md).
     > 
     > If this option is enabled, dynamic user creation still occurs even when SAML user attributes have not been set for all IdP users. To prevent a user from being automatically created, your SAML IdP must deny the user access to SAP Datasphere.
 
 
@@ -2,7 +2,7 @@
 
 <link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
 
-# Exporting Users
+# Export Users
 
 If you want to synchronize SAP Datasphere user data with other systems, you can export the data to a CSV file.
 
 
@@ -2,9 +2,9 @@
 
 <link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
 
-# Importing or Modifying Users from a File
+# Import or Modify Users from a File
 
-You can create new users or batch-update existing users by importing user data that you have saved in a CSV file.
+You can create users or batch-update existing users by importing user data that you have saved in a CSV file.
 
 
 
@@ -14,7 +14,7 @@ The user data you want to import must be stored in a CSV file. At minimum, your
 
 If you want to assign new users different roles, include a `Roles` column in the CSV file. The role IDs used for role assignment are outlined in [Standard Roles Delivered with SAP Datasphere](standard-roles-delivered-with-sap-datasphere-a50a51d.md).
 
-For existing users that you want to modify, you can create the CSV file by first exporting a CSV file from SAP Datasphere. For more information, see [Exporting Users](exporting-users-e227d3c.md).
+For existing users that you want to modify, you can create the CSV file by first exporting a CSV file from SAP Datasphere. For more information, see [Export Users](export-users-e227d3c.md).
 
 > ### Note:  
 > The first name, last name, and display name are linked to the identity provider, and can't be changed in the User list page, or when importing a CSV file. \(In the User list page, those columns are grayed out.\)
Original file line number	Diff line number	Diff line change
`@@ -303,7 +303,7 @@ SAP Datasphere can be hosted on non-SAP data centers.`
`303`	`303`	`When dynamic user creation is enabled, new users will be automatically created using the default role and will be able to use SAML SSO to log onto SAP Datasphere. After users are created, you can set roles using SAML attributes.`
`304`	`304`
`305`	`305`	`> ### Note:`
`306`		`- > Automatic user deletion is not supported. If a user in SAP Datasphere is removed from your SAML IdP, you must go to Security \> Users and manually delete users. For more information, see [Deleting Users](deleting-users-3ceb94c.md).`
	`306`	`+ > Automatic user deletion is not supported. If a user in SAP Datasphere is removed from your SAML IdP, you must go to Security \> Users and manually delete users. For more information, see [Delete Users](delete-users-3ceb94c.md).`
`307`	`307`	`>`
`308`	`308`	`> If this option is enabled, dynamic user creation still occurs even when SAML user attributes have not been set for all IdP users. To prevent a user from being automatically created, your SAML IdP must deny the user access to SAP Datasphere.`
`309`	`309`