web
You’re offline. This is a read only version of the page.
close
  • the ability to calculate dates and set dynamic conditions that would change the records reflected in the view.

    This is a feature when creating a view or filtering a view.

    It would be nice to have the ability to calculate dates and set dynamic conditions that would change the records reflected in the view.


    For example, create a view with the condition "Records created from 10:00 last week Monday to the present".

    "Monday at 00:00 shall be the time to switch weeks."


    The records reflected in the resulting view would be

    The records that will be output at 23:59 on this Sunday are those that have been updated between 10:00 on last Monday and 23:59 on this Sunday.

    Records updated between 10:00 on last Monday and 00:00 on this Monday will be output at this Monday 00:00.


    Setting such conditions in the view and having a function that automatically switches records will improve user convenience.

  • Display a pivoted table using views, etc.

    The ability to view a vertical Dataverse table as a horizontal pivot table using views, etc. is not currently implemented.

    The addition of this feature will make it easier and more convenient for users to work with the data.

  • The ability to export data from tables and graphs displayed in Resources > Overview in the Power Platform Admin Center to CSV files, etc.

    The ability to export data from tables and graphs displayed in Resources > Capacity > Summary > Overview in the Power Platform Admin Center to CSV files, etc. is currently not implemented.

    The addition of this feature will make it easier for users to analyze Dataverse usage and license usage.

  • It would be useful to be able to generate a URL so that we can fix the tab that opens when the form is loaded.

    It would be useful to be able to generate a URL so that we can fix the tab that opens when the form is loaded.

    For example, when opening a sales case form, I would like to select the "Estimates" tab, which is the third tab in the tab order, so that it always opens when the form is loaded.

  • Maintenance mode for model-driven apps

    Maintenance mode for model-driven apps is not currently implemented.

    You can disable the app, but users who know the URL will still be able to access it directly.

    If a maintenance mode is implemented, it would be a useful feature for both end users and developers.

  • Disable duplicate detection of Appointment records

    Appointment records have duplicate detection built into the system, and when importing an appointment created with Outlook integration or a record from Excel, unable to change settings so that records can be automatically saved ignoring duplicate dates and times and a message duplicate detection is displayed.


    It would be easier for users to incorporate appointments if they could change settings related to duplicate detection and message display for Appointment records.

    (e.g., disable duplicate record detection altogether, or only disable duplicate date/time detection in Outlook integration or Excel import).

  • Functionality that causes an error when trying to import in Excel if the value of a required columns is missing.

    Currently, if I do an Excel import with no values for the required columns, the record can be saved without any errors or other problems.

    The ability to save records without the values of required columns may prevent customers from accurately understanding the information.

    Implementation of a function that displays an error when importing a record with no value for a required field will make the application more convenient to use.


  • Get column checksum data from OData

    Currently, row checksums are created when doing an Excel export and are not present in the table.

    However, placing the row checksum in the table, via a connection to OData, would allow for the following actions.


    1. Connect the information in the Power Apps table to Excel by acquiring data from Odata.

    2. Use PowerQuery in Excel to prepare an Excel file with the same information as the view of the Power Apps application in use.

    3. If you want to modify the records in the table, modify the data in the Excel format.

    4. Import the corrected Excel file into PowerApps using Excel Import.


    This allows data modification through the Excel format when the table within Power Apps is not to be directly modified by an unspecified number of users.

  • Get column checksum data from OData

    Currently, row checksums are created when doing an Excel export and are not present in the table.

    However, placing the row checksum in the table, via a connection to OData, would allow for the following actions.

     

    1. Connect the information in the Power Apps table to Excel by acquiring data from Odata.

    2. Use PowerQuery in Excel to prepare an Excel file with the same information as the view of the Power Apps application in use.

    3. If you want to modify the records in the table, modify the data in the Excel format.

    4. Import the corrected Excel file into PowerApps using Excel Import.

     

    This allows data modification through the Excel format when the table within Power Apps is not to be directly modified by an unspecified number of users.

  • Set up multiple organizers for Teams webinars

    Currently, when creating a webinar as an event, only one organizer can be set up.

    Although co-sponsors can be set from Teams after the event is created, it would be more convenient for users if all co-sponsors could be set at once during the event registration process in Dynamics 365.

    Also, it is not possible to change the details of the co-organizers (e.g. date and time), so it would be more convenient to be able to set multiple co-organizers.