2.4 Bulk Record Operations, Data Import, Export & Templates

Bulk Record Operations, Data Import, Export & Templates

Enterprise business applications require efficient mechanisms for importing bulk data, synchronizing with external sources, performing bulk maintenance, and exporting data for analysis. In Microsoft Dataverse, functional consultants must master the spectrum of data ingestion tools, Bulk Record Deletion system jobs, and Excel Export modalities.

---

1. Data Ingestion Modalities in Dataverse

Depending on data volume, transformation requirements, and technical skill, consultants select from several ingestion pathways.

+-----------------------------------------------------------------------------------+
|                         DATAVERSE INGESTION PATHWAYS                              |
|                                                                                   |
|  [INGESTION SCENARIO]                                                             |
|        |                                                                          |
|        +---> Ad-hoc, one-time user upload (Excel / CSV)                           |
|        |     ---> MODERN IMPORT / GET DATA FROM EXCEL                             |
|        |                                                                          |
|        +---> Complex transformation, scheduled ETL, on-prem gateways              |
|        |     ---> POWER QUERY DATAFLOWS (M Engine)                                |
|        |                                                                          |
|        +---> Enterprise big data, high-scale pipeline                             |
|              ---> AZURE SYNAPSE LINK / DATA FACTORY / FABRIC PIPELINES            |
+-----------------------------------------------------------------------------------+

Ingestion Method Comparison

---

2. Column Mapping, Lookup Resolution & Choice Sets

When importing data via CSV or Excel, mapping source columns to target Dataverse attributes requires special attention for complex column types.

+-----------------------------------------------------------------------------------+
|                     LOOKUP & CHOICE MAPPING ARCHITECTURE                          |
|                                                                                   |
|   [SOURCE ROW]                 [DATAVERSE MAPPING]            [TARGET TABLE]      |
|                                                                                   |
|   "Acme Corp" (Text)    --->   Match against Primary Name ---> Account GUID       |
|                                (or Alternate Key)              (Parent Account)   |
|                                                                                   |
|   "Tier 1 Customer"     --->   Map Text Label to Integer  ---> Option Value: 1001 |
|                                (Choice Set Option)             (Customer Tier)    |
+-----------------------------------------------------------------------------------+

Resolving Lookups and Choice Columns

1. Lookup Fields:
   • During import, Dataverse matches text values against the Primary Name Column of the related table (e.g., matching text "Fabrikam" to an Account record named "Fabrikam").
   • If duplicate records exist with the same name in the target table, the lookup resolution fails or links ambiguously.
   • Alternate Keys: To ensure exact matching on natural keys (e.g., Customer ID or Social Security Number), define an Alternate Key on the target table and map the lookup against that key.
2. Choice (Option Set) Fields:
   • Dataverse allows mapping incoming text labels to the corresponding integer values in the target Choice column.
   • If the source file contains an unmapped choice label, the import can be configured to fail the row or add the new option into the Choice definition (if permissions allow).

---

3. Bulk Record Deletion Jobs

Bulk Record Deletion enables administrators to remove large volumes of obsolete, inactive, or non-compliant records asynchronously without manual row-by-row deletion.

+-----------------------------------------------------------------------------------+
|                    BULK RECORD DELETION JOB CONFIGURATION                         |
|                                                                                   |
|   1. DEFINE QUERY:                                                                |
|      Select Table: [Lead]                                                         |
|      Filter: [Status Equals 'Disqualified' AND Modified On Older Than 2 Years]    |
|                         |                                                         |
|                         v                                                         |
|   2. CONFIGURE SCHEDULE & OPTIONS:                                                |
|      - Job Name: "Monthly Purge of Stale Disqualified Leads"                     |
|      - Start Date & Time: 2026-08-20 02:00 AM                                     |
|      - Run this job every: [ 30 ] days                                            |
|      - Send an email notification to: [ admin@contoso.com ]                       |
|                         |                                                         |
|                         v                                                         |
|   3. SYSTEM JOB EXECUTION & MONITORING:                                           |
|      Status: Waiting ---> In Progress ---> Succeeded / Failed                     |
+-----------------------------------------------------------------------------------+

Practical Bulk Delete Scenarios:

• Regulatory Compliance (GDPR/CCPA): Purging customer personal data upon expiration of statutory retention windows.
• Storage Optimization: Removing completed asynchronous workflow logs, transient sync records, and old email attachments.
• Data Hygiene: Deleting closed test records or disqualified leads.

[!CAUTION] Cascading Delete Behaviors: Bulk deletion honors table relationship cascading rules. If an Account is deleted and the relationship to Contacts is configured as Cascade All, all associated Contact records will be permanently deleted as well. Always verify cascading behaviors prior to running bulk delete jobs.

---

4. Excel Export Modalities & Security Governance

Model-driven apps provide four distinct ways to export data to Microsoft Excel.

+-----------------------------------------------------------------------------------+
|                         EXCEL EXPORT MODALITIES MATRIX                            |
|                                                                                   |
|  +------------------------+  +------------------------+  +---------------------+  |
|  |    STATIC WORKSHEET    |  |   DYNAMIC WORKSHEET    |  |  OPEN IN EXCEL      |  |
|  |                        |  |                        |  |       ONLINE        |  |
|  | - Snapshot in time     |  | - Live query connection|  | - In-browser edit   |  |
|  | - Up to 100,000 rows   |  | - Requires Dataverse   |  | - Click 'Save' to   |  |
|  | - No live data refresh |  |   authentication       |  |   sync back to DB   |  |
|  +------------------------+  +------------------------+  +---------------------+  |
+-----------------------------------------------------------------------------------+

Comparison of Export Types

Security & Privilege Governance

• Export to Excel Privilege: Located under the Business Management tab of Security Roles. If this privilege is removed, the entire Export to Excel menu is hidden from the user.
• Field-Level Security: Columns protected by Field Security Profiles export as masked values (e.g., ****) if the user lacks Read privilege on the secured column.