Table Creation Permissions
Currently, there is no implementation of the ability to enable the following scenarios:
Developer A: creates tables 1 & 2
Developer B: creates table 3
Developer A would only be able to view and edit tables 1 & 2, but will have no permissions to table 3. Dev...
Filter related records in an editable grid.
Currently the functionality for the following scenario is not implemented
When using the editable grid, when viewing view A of table A, selecting an item in table B should filter the item in the associated table C.
Adding this feature would improve convenience...
プライマリ名列の代わりにルックアップフィールドに別の列を表示する
Currently, the functionality of the following scenario is not implemented.
There are two tables, Table A and Table B.
This is a 1:N relationship.
The lookup field should display values other than the primary column.
Adding this functionality would ...
Display another column in the lookup field instead of the primary name column.
Currently, the functionality of the following scenario is not implemented.
There are two tables, Table A and Table B.
This is a 1:N relationship.
The lookup field should display values other than the primary column.
Adding this functionality would ...
Allow multiple files to be attached to a column
Currently we are not able to attach multiple files to the Dateverse column, so we are attaching multiple files separately.
This can be a very time consuming process and should be streamlined by allowing multiple files to be attached at once.
Adding this feature would be a convenien...
Microsoft Dataverse language collations are not case-sensitive for Japanese.
Currently, Microsoft Dataverse language collation order is not case-sensitive for Japanese.
It would be reasonable for users if this feature were added.
Microsoft Dataverse language collations are case-insensitive.
The collation order of the Dynamics database is determined at instantiation and cannot be changed thereafter.
Therefore, it cannot be case-sensitive.
Allowing these changes will improve user convenience.