on
RE:
that's a bugfix request, not an idea.
RE:
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
RE:
Very much needed improvment! (Y)
RE:
Great idea! Admins now are lacking information about successful publication, this would help!
RE:
I have used Fabric SQL Endpoint to store the metadata in form of View to bulk copy data from ADLS Gen 2 to Onelake using Fabric Data Factory.Kindly let me know if you want to have a walkthrough, I would be happy to share.My alias - avadhkishore
RE:
Ignore. Not a bug.
RE:
This, indeed, is a necessary feature from the point of view of control and credibility in enterprise-level governance.
RE:
Yes this basic feature would be very helpful.I give my vote too.On other side I understand that Microsoft prefer making money by indirectly forcing its customer migrating to Sharepoint.
RE:
@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.
RE:
good idea