洋紀 相原

Currently, in Dataverse environments (via make.powerapps.com), administrators cannot disable or hide the Import button on a per-table basis through configuration.

In certain scenarios, due to governance policies, data integrity requirements, or operational constraints, organizations may want to restrict the Import functionality for specific tables only. However, since the Import button is always visible and active, users may attempt to upload files to tables where importing should not be allowed, leading to confusion, failed operations, or unintended data issues.

We would like to request the ability for administrators to:

- Disable the Import button per table via configuration

- Hide the Import button for specific tables based on role or settings

- Optionally enforce validation earlier in the upload process to prevent unsupported imports

Providing per-table control over the Import functionality would improve governance, reduce user confusion, and enhance overall UX by preventing invalid actions before they occur.

Thank you for considering this enhancement.

Currently, importing data in Excel (.xml) format is not supported across Dataverse tables.

In many business scenarios, Excel-based files are widely used for data migration, bulk updates, and operational data management. In particular, Excel (.xml) format files are commonly generated from external systems and internal data processing workflows.

However, since Excel (.xml) format import cannot be executed at the table level in Dataverse, this limitation creates additional operational steps, format conversions, and administrative overhead.

We would like to request support for importing Excel (.xml) format files across all Dataverse tables.

Enabling this capability would improve operational flexibility, streamline data migration processes, and enhance overall usability for organizations managing structured datasets.

Thank you for considering this enhancement.