Share your ideas and vote for future features

I have received the following email. The screenshot is in Japanese, but the content is about Dataverse exceeding capacity. Since I only use the Power Platform plan included in Office 365, I do not want to receive such emails in the future. For those who only use the Power Platform products with Office 365, I don't think this email is necessary, so please consider implementing a function that allows us to choose whether or not to receive it as soon as possible. Thank you, <the content of the email> Database is running out of space As of April 12, 2021 0:00:26 UTC, your tenant is using 100% of the available storage capacity of the Database (3.55GB/0MB used). Please take immediate action and continue to operate without interruption. What happened? Your tenant is using nearly all of your Microsoft Dataverse (formerly Common Data Service) capacity. Dataverse storage for tenants includes all types of environments except trial, preview, support, and developer. The most common cause of capacity loss is applications using the increased amount of storage. Find out more about what happens when you exceed your storage capacity. How do I fix it? Review the report on storage space usage. Reduce the amount of storage space you use by deleting or erasing different types of information. Find out how to add capacity and purchase it for your organization. Troubleshooting Find out where storage is being used throughout your environment.   ... View more

We are able to edit optionset values using the Solution Explorer but it appears that functionality hasn't been added to the Makers Portal. This is something we've come to rely on and would face some issue if access to the Solution Explorer is removed before this is added to the Makers Portal.  ... View more

Background The purpose of an embedded canvas app is to have a low code/no code solution to custom UI components in model-driven forms instead of building something completely custom with HTML or PCF. To have a seamless experience for end-users, the embedded canvas apps should be styled the same as model-driven forms and be transparent that there another app within the model-driven form . The embedded canvas app is designed to be responsive irrespective of the device. Hence when viewed on larger screens, all the controls fit in the screen and the scrollbar is not required and when viewed on smaller screens such as laptops, scrollbar must appear only to show the controls that are not visible in the screen.    Problem and Feature Request Presently on larger screens, an unwanted vertical scrollbar appears introducing a large chunk of white space within the canvas app which creates a confusion for the user having to scroll and check if there are more controls on the form and defeats the purpose of having a responsive embedded canvas app. The embedded canvas app and/or model-driven form should remove and adjust the height to the embedded app and scale accordingly. Example:   Also if we have some model-driven form fields/columns/attributes below the canvas app, then this would give an horrible user experience since the user will have to scroll through all the white space to reach the field:   The amount white space added is huge and cannot be ignored since it spoils the UI. Similar is the case in smaller screens as well. If the users needs: to scroll to view the whole content embedded app when there's space on the model-driven form or app has redundant scroll bars and/or needs to scroll below the embedded app to enter the data then it defeats the purpose of embedded canvas apps and would better to revert to a custom HTML or PCF control. ... View more

The decimal field type only lets you use values between -100 million and 100 million.   This is way too small for the data we want to import - any financial reporting solution will find this limit difficult to work work.   Please increase the size of this column type to be in the 10s or even 100 billions range. ... View more

I am creating a data table in a Power Apps application using Dataverse as the data source.   When I set the MyProfile function (Office365Users.MyProfile().DisplayName) to the Filter function, the following error appears and the result is not displayed.   "Warning about delegation. The Filter portion of this formula may not work properly with large data sets." I am looking to use the Filter function in more situations. Therefore, I would like to be able to use the MyProfile function in the Filter function. ... View more

Currently, the only way for users to add columns is to Open Advanced Find (which moves them out of Unified Interface) and use the very old and cumbersome way to add a column to a view which is not intuitive (e.g. rearranging, resizing takes multiple attempts before it looks right). Especially for ad-hoc adjustments (e.g. I quickly want to add one more column, just temporarily) this is cumbersome and not intuitive. The new view editor in PowerApps is nice, but only available for Admins.    Please add a feature to add columns ad-hoc to any view and to rearrange them. If the user made a change, add the same asterisk (*) to the view name (the same way it is added when the user changes the filters in the new filter pane). Then allow users to save the changed columns and filters as a new view from the ribbon via  "Save as new view" command.  Together with the new filter pane, this would eliminate the need for Advanced Find and provide a more streamlined unified interface experience. See quick mockup below.    ##       ... View more

I set some columns to be required columns on Dataverse. 'Required' worked well, except for lookup columns. There are dropdown box for column requirement options even when I make new lookup columns. However, when I tried to create a new record on Power Apps using Patch or Collect function, record without required data in lookup columns was able to accepted without any error. Thus I need to see if there are any blank for these columns on Power Apps so far. I appreciate if Dataverse itself would reject a new record with blank in required lookup columns. ... View more

Ability to create a sandbox environment copy with randomized or a date range of partial data instead of Full Data or No Data. This will help with online sandbox storage consideration and minimize nonvalue add administrative overhead to create bulk deletion jobs post copy. Also, post bulk deletion jobs can take weeks or months to reduce a large database/CDS. This will also allow sandbox environment data to be more current versus working and validating processes against stale data. Loading/importing sample data is not an ideal solution for such scenarios as email to case, sharing data to access teams, and testing cascading relationships.    Another challenge with bulk deleting data post copy is due to the temporary overage of online/CDS storage, another instance copy cannot be performed until the CDS storage is back within available capacity. This negatively impacts the ability to process a support instance copy for MS support since an error prompt stats no available capacity to process a support instance copy.   This is a similar request posted in prior Ideas post: https://experience.dynamics.com/ideas/idea/?ideaid=43f715b5-8a01-ea11-b862-0003ff68edfa ... View more

Currently, Export To Data Lake does not support relationship setting. is it possible to consider enabling this feature in the future, please ?   Thanks ... View more

Ability to leverage the new Dynamic M-Query Parameters in Power BI with the Dataverse Direct Query functionality which would allow Power BI reports embedded into Power Apps & Dynamics 365 showing live data. (CDS)   No more hacks with power automate & power bi premium to trigger data source refreshes etc. ... View more

To Microsoft: you have an army of super developers, if Microsoft would just focus a small set of resources to enhance the user experience by adding functionalities like this one by providing out-of-the-box controls/components, PowerApps would rule.   I hope you could consider to have the drag-and-drop functionality for Documents with SharePoint integration.   It would enable model-driven apps to drag-and-drop files easily, and also while using the Dynamics 365 App for Outlook. This would make super easy for users to drag-and-drop files from the windows file explorer -or- an email to the model-driven app interface and store the files in the connected SharePoint in the back... See screenshots below for reference.   From Windows File Explorer to a model-driven app; (related) Documents control with integration to SharePoint...   From the Outlook inbox - email attachment to the model-driven app through Dynamics 365 App for Outlook.   Thank you for your cosideration. Best, cepjc   ... View more

Apparently the Auto-map button works only for built-in CDM tables but I wouldn't know because I don't use them.  One think I can say is that it never works for custom tables. (maybe because of the publisher's prefix?).  It might be considered a bug but I'm publishing it here as an idea because it will greatly improved the current auto-map feature.     see also : Solved: Re: Auto-map never works in dataflows, doesn't it? - Power Platform Community (microsoft.com)   Thank you --mo ... View more

Allow us to string mutliple levels of lookups in Dataverse tables using the not notion. Ex : sale.product.productSubCategory.productCategory.Title   Data modeling is unnecessairly complex (and ugly) without this feature. ... View more

Would be very handy to have the ability to trigger Dataverse Dataflow from Power Automate. Sometimes the Dataflow refresh/scheduled run  do not satisfy the requirements and the trigger needs to run based on some business logic such as when a file is uploaded or when an event occurs in the system.   ... View more

It would be great to get the description in the DataSourceInfo function for any field/column for a specific Table.   Right now, the DataSourceInfo gets you a lot of other metadata like the displayname, max length, max value, min. value, etc.. Adding the description to this list would make the list complete.   The description can then be used for HintText or for tooltips to improve accessibility . ... View more

Change the dropbox field to a non-primary column in EditForm.   Example:  The main table is A, and the referencing table is B. Let the primary column of B be b and the column to be looked up be w. A(many) : B(1) and w is set as the lookup column.   The property settings for the app dropbox are as follows. Edit field is changed from default column b to column w.   I want this setting to work without displaying an error message. ... View more

Context The purpose of an embedded canvas app in a model-driven form is to have a low code/no code solution to custom UI components in model-driven forms instead of building something completely custom with HTML or PCF. To have a seamless experience for end-users, the embedded canvas apps should be styled the same as model-driven forms and leverage the same events (e.g. refresh, save) and actions (ribbon aka command bar) as the model-driven form.    Problem or Feature Request ModelDrivenFormIntegration provides a lot of useful methods to reference the model driven form context and OnDataRefresh event, but the most basic event is missing, the save event. The model-driven form Save event does not save the canvas apps data event even on OnDataRefresh, and the only workaround approach is to manage the save within the embedded canvas app individually and introduce another save button. From an user experience(UX) standpoint, it makes little sense to have two Save buttons and user needing to click “Save” twice; once for the data entered in the canvas app and one for the model-driven form. Users get confused which save does what and why there are two saves, users forget to click save on the embedded canvas apps, and therefore loses changes. Having another Save or other action within the embedded app fails to serve the purpose of embedding the canvas app!   Please have the ability to register to the model-driven form save event and have a OnDataSave action property in the ModelDrivenFormIntegration! ... View more

It would be great if you could work with decimal fields on computations and round(), floor() or ceil() the result to use on a Whole Number field or with other functions. ... View more

When the year is included in an autonumber, include a setting to reset the autonumber seed value at the begining of every new year.   example: 2020-01000, 2020-01001, 2020-01002, ... 2021-01000, 2021-01001, ... ... View more