-
Redo button or edit width of Business Process Flow
If you click on a lookup field (for any entity), you can click on the magnifying glass or on the cross. You click quite easily on the cross, so that the existing value is immediately removed. This is because the width in the steps of a Business Process Flow is very narrow.
You cannot restore this with a button. You can only leave the record immediately and not save the changes. If it is a required field, you are in luck, because then the record will not be saved if the field is not filled. If it concerns a non-mandatory field, the record may now have been automatically saved and you can only look up the old value from the control history. That is very difficult for users and consumes a lot of time to recover the original value of the field.
As a user you cannot see the content of the value without hovering over it. Also the cross and the magnifying glass are quite near each other. The wish of one of our customers is to make the content of the value more clear, or change the position of the cross so that it is not so near to the magnifying glass anymore. However, best option would be a redo button during the session that you are editing a record.
Thanks in advance.
-
In Dataverse Search, get the option to set the priority of entities for the tabs in the search results
Dataverse Search has an excellent algorithm where it shows the order and priority of tabs on top of the search results. However, it seems that the search engine not always shows the most relevant tabs on first place. The customer I work for uses the entity Adminstrations and this entity has a big focus in the system. When you search for the name of the Administration, you will find more results and more important results for this entity, but still it shows the entity Contacts (Microsoft entity) on first place. Same with Accounts on some search results. Sometimes Administration is the 7th tab, even though search results are much more important for the user.
The customer requested to update the order of tabs, but this doesn't seem possible. It would already help if the algorithm doesn't make a difference between Custom entities and Standard entities provided by Microsoft. Next to that it would help if you can set the priority for Dataverse Search per entity.
Thanks.