-
Ability to create multiple invoices from the last 12 months' worth of orders
Currently, the ability to generate multiple invoices from the last 12 months' worth of sales orders has not been implemented.
When this feature is implemented, multiple invoices can be created from a single order record, which is more convenient for customers.
-
Show marketing form in the preview
Currently, there is no standard way to show a marketing form in the preview.
Since the preview function is intended to be used as a test page, We would like it to be improved as a standard function so that the marketing form linked to the event is displayed in the preview.
Once this behavior is implemented, can make changes and fixes during preview.
-
Automatically set record owner to superior department when subdivision is disabled/deleted
If the department is abolished when the department is abolished, I would like to automate the process of reassigning the specified record to the specified department with the deletion as a trigger.
Currently, I feel that it is inefficient because it requires manual operation in advance.
-
Ability to change ownership of model-driven apps
If the URL of the application has already been distributed as a shortcut and the owner can be changed without deleting the application, the URL will not be changed and the application can be used continuously without redistributing the URL.
-
Ability to set the default value of the Add to Queue dialog to empty
With the April 2023 update, the queue search now has an automatic value set, but we would like to add the ability to revert that setting.
The update should remove the default search value.
-
When filtering by "CreatedOn" and including "Equals" in the search condition, the seconds cannot be set and the search cannot be performed.
When filtering by "CreatedOn", seconds are included in the search condition, but when searching, only minutes can be set.
Searches must be modified to run in minutes or seconds.
-
Enable to edit item display names (start date, end date, etc.) in the "Copy Time Entry" dialog box, etc.
After clicking the week copy button on the "Time Entry" screen, I would like to be able to edit the item's display name (start date, end date, etc.) in the "Copy Time Entry" dialog box, etc.
We hope to make it easier to understand and use.
-
About customizing the dialog box after clicking the copy week button on the time entry screen of the Project Operations app
On the time entry screen of the Project Operations app, click the Copy Week button in the dialog box "Start Week", "Start Date", "End Date", etc.
The display name is confusing to users, so the weekly copy feature is not familiar to users.
From the above, we want to make the display name easy to understand that the start week is the period of the copy source and the end collection is the period of the copy destination.
We ask that developer allow customization of the dialog box or change the display names such as "Start Week", "Start Date", and "End Date" to more descriptive display names.
-
The Dynamics 365 Excel export timeout limit needs to be increased.
Current Dynamics 365 Excel export timeout has an internally hardcoded timeout of 12 minutes.
Because the 12 minute timeout is the default behavior, it is not possible to change the Excel export timeout value.
Therefore, we need the ability to increase the Dynamics 365 Excel export timeout limit.
With this implementation, the export limit will no longer time out at 12 minutes, allowing companies to work without worrying about the export limit and improving work efficiency.
-
When customer information is merged, a log of the merge is also recorded in the primary audit log.
Request to Reference Non-Primary Information from Primary Audit Logs
There are customer records A and A’, with A being the primary. When merging, only the information from A is adopted, and no integration event is recorded in A’s audit history. If the merge itself was an error or if you want to check A’s information, you will need to search for the inactive customer information, which becomes difficult over time. Without a merge log on the primary side, there is a risk of not realizing that an incorrect merge has occurred.
Therefore, We propose that a merge log be recorded on the primary side as well, allowing reference to the non-primary data.