Power Platform Governance and Administration

Problem definition A document of around 15.000 lines has been imported. Of which 6.500 indicate an error. Customers want to investigate these error records on the reason why, fix the error, and import them again. However, when exporting the information about the error lines, an export of 4.000 lines is generated instead of 6.500 error lines as indicated in the overview. Solution The advise for now is to import in batches around 2.000-3.000lines. But some customers have a lot of data to import. So when they need to break it down to batches of 2.000-3.000lines, it will take more time. Wish It would be nice if it could be possible to import in larger amounts without breaking down/over process the system.

Into Power Platform Admin Center, today it is possibile to add only one user per time, accessing: Power Platform Admin >> Environment >> Settings >> User. It is very useful to have the possibility to add multiple users maybe just indicating user values separetad by comma, eg: user1, user2, user3, etc....

Please add Russian language support to AI BUILDER and Azure Cognitive Services.

We are aware that the setting to read the Power Apps portal site with QR code or barcode is not currently feasible within Power Apps. When guiding the Power Apps portal site on a smartphone or tablet, it can be simplified and the range of guidance to customers is expanded.

Dont tell me im using an old version of edge/ie when im not using either one. Mostly because IE is shit and edge is bloat. PS: maybe actually parse the user agent string and dont just assuma its an old edge version if you dont know the user agent string

Currently when working with Customer Service/Omnichannel Session Tabs the behavior is that the tab content will reload every time the tab is selected/had focus. This is documented as by design: "Why do tabs reload when an agent switches session tabs or switches from session tab to widget?" This is to make sure that the updated data is available for the agent at all times source: https://docs.microsoft.com/en-us/dynamics365/customer-service/channel-integration-framework/faq-channel-integration-framework#why-do-tabs-reload-when-an-agent-switches-session-tabs-or-switches-from-session-tab-to-widget Of course this does make sense for a lot of implementation scenario's, when using the tab to display a real-time dashboard for instance. But in our scenario we are using the Session Tabs to enable access to back-office data from other applications using Canvas Apps. This does really benefit the user experience. But currently the Canvas Apps are reloaded every time the user switches between other tabs or sessions, hence the context in the Session Tab is lost and the user will have to lookup/drill-down the back-office data again, while this data is fairly static. It would be perfect if we could configure this behavior for every tab, as we do with the behavior for the ability to close tabs for instance.

Dataverse activities can surface in the Compliance centre but are practically unusable. 1. Activities can be system or user generated, there can be 000's of system and '00's of user created. There is no filter to only reveal user activities so a lot of junk has to be exported to Excel. 2. All Dataverse activities are classed as Dynamics/365 activities, this includes logins and other non-dataverse table related activity. Again a lot of junk has to be exported with real data. 3. We have 81 environments that can log table activity into the compliance centre. There is no way to filter and separate out specific environments. 4. We want to look at activity on specific tables but there is no filter that allows this. 5. We want to look at specific record activities CRUD but there is no filter for this. Not the most helpful of data structures. This is a one record table create {"CreationTime":"2021-12-06T20:33:11","Id":"f8aa0752-036e-4af0-a026-01be0d0b3bbf","Operation":"CrmDefaultActivity","OrganizationId":"f67feaf5-3c41-44ef-8bae-64792f501e0a","RecordType":21,"ResultStatus":"Success","UserKey":"10032001B571C736","UserType":0,"Version":1,"Workload":"CRM","ClientIP":"119.151.198.139","ObjectId":"Create crec0_vessel","UserId":"prince.charles@tack.co.uk","CrmOrganizationUniqueName":"org44de3f34","Fields":[{"Name":"crec0_tonnage","Value":"44444"},{"Name":"crec0_length","Value":"300"},{"Name":"crec0_ship","Value":"BigShip"},{"Name":"crec0_captain","Value":"TopCaptain"},{"Name":"crec0_name","Value":"1006"},{"Name":"crec0_vesselid","Value":"01441cb4-d356-ec11-8f8f-000d3aa9d062"}],"InstanceUrl":"https:\/\/tt8.crm4.dynamics.com\/","ItemType":"Dynamics365","ItemUrl":"https:\/\/tt8.crm4.dynamics.com\/main.aspx?etn=crec0_vessel&pagetype=entityrecord&id=01441cb4-d356-ec11-8f8f-000d3aa9d062","UserAgent":"Mozilla\/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/96.0.4664.55 Safari\/537.36 Edg\/96.0.1054.41","CorrelationId":"00000000-0000-0000-0000-000000000000","EntityId":"01441cb4-d356-ec11-8f8f-000d3aa9d062","EntityName":"crec0_vessel","Message":"Create","PrimaryFieldValue":"","Query":"","QueryResults":"","ServiceContextId":"00000000-0000-0000-0000-000000000000","ServiceContextIdType":"","ServiceName":"Dynamics365","SystemUserId":"68d4ad99-6853-ec11-8c62-002248811e29","UserUpn":"prince.charles@tack.co.uk"}

It would be nice if on the inbox view, if we could filter out closed cases. This would greatly help the efficiencies on our customer service team!

Before raising the idea let's state what is working well with Patch Solutions > Patches can create or update elements in a solution without having to deploy a full upgrade solution - GREAT > Patches can not delete fields in the target environment - OK - that's obvious > Patches can remove fields from a form if they were added to the form within a full solution But, there's one thing that not working - and that's annoying. > If you have introduced a field using patch on a form, it will not be removed by any other patch So, my wish is that Patch Solution can update ANY form in ANY way without any limitations And I think this must be doable for the following reasons * My understanding is that forms are stored as XML - so, a Patch "just" has to replace the full XML, without additional magic that does som ekind of merge inside the xml Please go for this as this might help a lot in the administration

Needs to be able to anonymize a contact without removing the contact due to the importance of statistical data. We need to be able to delete the audit log for the specific contact. The plan is to anonymize the name and remove contact information, all activities and the audit log.