Kunihiko Hayakawa ESCAL ENG

For datetime fields the user can click on the calendar icon to display a calendar. On this control the user can navigate by clicking on the next/previous month buttons. However there is no way to specify a year so it is very tedious for the customer to select a date that is not in the current year. Consider adding an ability in the calendar control to jump to a specific month and year.

This is a UCI specific issue and it does not occur in WebUI. When clicking on the calendar icon for a datetime field a calendar control will be displayed to the customer. The customer can click on the up and down buttons to switch to the previous and next months. Some months display more dates than others and the calendar control will expand upward to make more space to display the extra line of dates. For instance 05/2019 displays 5 rows of dates but 06/2019 displays 6 rows. So when a user presses the down button when on 05/2019 the control will expand upwards and in so doing the up and down button positions will also shift upwards. This makes it difficult for the user to navigate to a date that is far in the future or past since the button position keeps shifting. Consider expanding the calendar control downward so that the up and down button positions do not change.

On the main form for the contact entity when viewed in UCI the First name and Last Name fields appear in the following order. First Name Last Name However, for the quick create form for the contact entity the order is reversed. Last Name First Name The default forms should maintain a specific order in which these fields should be displayed.

Since the changes described below were implemented lookup will display a list of the most recently viewed records when you click on the lookup. Preview for usability enhancements to lookups in Unified Interface https://powerapps.microsoft.com/en-us/blog/preview-for-usability-enhancements-to-lookups-in-unified-interface/ The most recently viewed records list is populated when a user opens a record. We would like a record to also be added to the list when it is set in a lookup even if the record itself has not been opened. From a perspective of a user a record that was set in a lookup is equally as relevant as a most recently used record as one that was actually opened.

Consider the following scenario 1. User opens an opportunity record with a subgrid of related activities 2. The user moves to the 3rd page of the subgrid and opens a related activity on this page 3. The user saves and closes this activity record and is returned to the opportunity record form 4. The related activity subgrid would display the first page of results We would like the ability to show the last viewed page in the subgrid when returning to form. Specifically in the scenario above we would like to be able to show the 3rd page of the subgrid on step 4 instead of the first page.

Currently users are able to create workflows that will cause an infinite loop. We should implement safety measures that would do one or more of the following: 1. When saving a workflow, have Dynamics evaluate the risk that the workflow will go into a infinite loop and warn the user. This warning can be shown for instance if fields like modifiedOn are used as a trigger 2. Automatically deactivate workflows that are determined to be in an infinite loop. This can be done if a workflow is seen to be executing a large number of times over an extended amount of time. If deactivation is too harsh of a measure we can send alerts to the admin.

Currently you can create teams via MS Flow but you cannot automate user team memberships. Please add the ability to add and remove users from Teams via MS Flow.

Our customer wants the ability to finely control what activity events are added to the Timeline. Specifically they would like to be able filter out activity events from an Account record Timeline that are related to activities tied to Contact records that are related to the Account record. The following is an example scenario that the customer would like to avoid in which an activity event is logged on the account record timeline. 1. User creates Account A 2. User creates Contact B that is related to Account A 3. User creates Appointment C that is related to Contact B 4. A post regarding the creation of Appointment C is added to the Timeline of Account A. ASK; Allow users to filter out activity events related to child records from the timeline but allow activity events that a directly related to the parent record.