Mahendra Krishnamreddy Seshadrireddy

Dear Microsoft Support, I'm having an issue with a sort order defined in a custom system view. The issue is with an Activity - we're sorting on actualend first and then createdon, the former is a date only field but the second is date/time. The order is not correct in the views. On one of the view had 2 date fields(Date completed & Date Created) and the sorting for that particular view was first sort by Date Completed and then by Date Created. The sorting was correct but We are expecting both the fields to be sorted by descending order. Currently Date field is calculating Hours minutes and seconds part in the server side. However we are expecting it should not calculate as mentioned above.

I am having an issue with the filter condition on Views, After creating a custom view I was trying to filter the view based on the owner selected, It is not searchable, if we had this functionality it would have been easy to add it as a filter in a view. Please try to implement this functionality in coming future releases.

We can create quote from account and contact entity if we go to related tab within the entity but If we have a Quote button called "Create quote" within account and contact entity, It would be very easy for the customers to create quote instead of going to related tab.

In Wave 2 release - We are not getting the dropdown list in Views while filtering, but this feature is available in Wave 1, We feel that old feature is good and easy for us to apply filters on views. It would be great if we get the old filters on Wave 2 also. In wave 1 - If we want to set any of the views as default, we just use to Pin it and it would set to Default, But In Wave 2 - We have to select the view and then click on the button to set the view as default - This is difficult for us to select that button everytime. It would be great if we get that Pinned feature again in Wave 2.

When ever we add a Flip switch control on Two option field, If we add the field on any of the form then A flip-switch control's color is grey when the field is read-only, and the value in the field is "yes". In version 9.0, when the value is "yes", the control is displayed in red regardless of whether the field is read-only or not. A similar behavior occurs in an "toggle control" control. It should be better if it will be possible to customize the color of certain read-only fields without changing the color completely for all the read-only fields.

Currently we are having a feature where we go-ahead and delete the audit log partitions on monthly basis, but our users are requesting to add a new feature where we should be able to delete the audit logs on daily basis because it is very difficult for the users to delete only required components, If we delete the current partition then it gets deleted everything, But we want a feature where we can go-ahead and delete only required components that too on a daily basis. Please consider this as a priority because we already have customers asking for this feature.

We have a field with the type Whole Number. When we search on this field with Categorized Search, the right results are shown. However when we enable Relevance Search (Dataverse Search) no results are shown because relevance search is only text based and we cannot search for numeric fields like whole number. Since Relevance Search will be mandatory in a few weeks with wave 2 update. We mainly search on this numeric type field. We are forced to use a search engine, that does not work for us. It would be very helpful for the users if we can search with numeric type fields in future through relevance search Because now we are forced to implement a workaround, by creating a text field and duplicate the Whole Number field to the new text field. Numeric type fields are the most used search field for us, Please implement the feature ASAP where we should be able to search with integer data type fields through relevance search.

We have created a N:N relationship with the same entity(Self referencing relationship), For example: We have an entity called Account and we have created a N:N relationship and we add this N:N relationship to a Subgrid, After that, add an existing or create a new record and save it, there must be 1 record created and if we open that record then we don't see the record in the other side. Our users are getting confused with the behavior that we have currently. It would be better if we have a behavior where the data gets populated on both the sides(If we have a record called called Test1 added to the subgrid and if we open the Test 1 record then the parent record should be populated in the subgrid of Test1.

Through N:N self-referencing relationship enable the possibility to have a sibling-like relationship instead of Parent/Child relationship (Many Parents, Many Children). For example: For Self-referencing N:N relationship on Contact On Contact A, on the sub-grid for the N:N relationship, when you add a record Contact B If you navigate to Contact B Current design: ------------------ Contact A is not seen  Desired outcome: ------------------------ To be able to see Contact A  Users are not happy with the current behavior, It would be better if we see Contact A on Contact B and contact B on Contact A.

Form footers in model-driven apps won't be supported with the 2021 release wave 2, It is deprecated, But It would be very helpful if we can get this Footer functionality back to Dynamics CRM. Please consider this as a feature request and do the needful.