0
Category:
STATUS DETAILS

Comments

Please extend the character count of the email field. We have clients running into this limitation.

Category:

Great idea! It would be great if it would be available for Spain.

Category:

Definitely this is necessary when we cover an invoice being transferred from Invoice Capture to the Invoice Journal in Dynamics.

Category:

that's a bugfix request, not an idea.

Category:

Better subject could be (but these ideas cannot be modified here), like my dear friend Niiranen just suggested: catalog/inventory of Copilot agents in tenant

Category:

Great idea! Admins now are lacking information about successful publication, this would help!

Category:

This, indeed, is a necessary feature from the point of view of control and credibility in enterprise-level governance.

Category:

@pitor KernerI am not sure what you mean but it could be the same thing as I am missing:Assume you have a case that is related to a contRact. Assume the contRact is associated to an account (firm). You can make a subgrid to add the contacts of that account to the case. This would bring up all the contacts in your system. To avoid this you can select only related records before you select contact entity and the view you have defined. However, this shows only the contacts that have been added to the case subgrid view as 'show related records' refers to the case. What we would wish is to be able to select the (custom) lookup field e.g. Account. Therefore it would automatically bing up a list of contacts on the case which are related to the account selected. This would be even more helpful if an account (company has 1000+ contacts and the users are not very IT literate to use ADF). maybe a bit similar like the quick view form but for the views.Another Scenario would be when you have a lookup field on the case form (not the regarding!) for an opportunity and you would like to see the quotes within that selected opportunity.For oversight/visibility purpose, I want to be able to see all related records from a (custom) lookup field record on a given entity form which is other than the regarding of that entity.

Category:

good idea

Category:

Expected behavior but bad user experience. I rather consider it as a bug as it already behaved differently in the past.

Category:

  • 1
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 500