Dynamics Community Forum Thread Details

Hi!

We've had 2025 Wave 1 for D365 rolled out over the past weekend. When using the Audit Summary View in the Auditing area of the Power Platform Environment Settings, I am getting an error. What I am trying to do is search for a specific user to see when they accessed the system.

Here are the steps I take:

1. Filter the view by Operation and select "Access" - successfully filters

2. Filter the view by Record

a. I've tried filtering by Equal and it won't allow me to even Apply it

b. I've tried filtering by Contains and it errors

c. I've tried filtering by Begins With and it errors

Error:

I've tested on two of my environments with the same result. Are others having this issue?

Secondary item: once you clear the filter, the filter greys out on the column so you can no longer filter until you refresh the page.

Notes:

- Region = Australia

- Version = 2025 Wave 1 (Server version: 9.2.25033.00192; Client version: 1.4.10056-2503.3)

Categories:

Dynamics 365 general

Hello Kit Englund,

Yes, it appears you've encountered a known issue with the Audit Summary View in Dynamics 365 (Power Platform) after the 2025 Wave 1 update. The error message "Encountered unsupported attribute name: 'objectidname' when converting entity expression to SQL" clearly indicates a problem with how the filtering on the "Record" (likely referring to the objectid and its related objectidname) column is being translated into a SQL query by the updated system.

Analysis of the Error:

The error suggests that the objectidname attribute, which typically holds the display name of the record being audited, is not being correctly recognized or processed by the underlying data access layer in the new version when used in filter conditions like "Equal," "Contains," or "Begins With." This is likely a bug introduced in the 2025 Wave 1 update.

Confirmation of the Issue:

Based on your description of consistent behavior across two environments and the specific error message, it's highly probable that this is a widespread issue affecting organizations that have upgraded to the 2025 Wave 1 release. You are not alone in experiencing this.

Why You're Seeing This:

The update likely introduced changes to the data model or the way the Audit Summary View constructs and executes its queries. The filtering mechanism on linked entity attributes like objectidname seems to have been broken or is expecting a different syntax or attribute.

How to Address the Issue (Workarounds and Next Steps):

Acknowledge it as a Potential Bug: Recognize that this is likely a bug in the 2025 Wave 1 release.

Report the Issue to Microsoft Support: This is the most crucial step. You need to report this issue through the official Microsoft support channels. Provide them with:
- Your region (Australia).
- Your exact version details (Server version: 9.2.25033.00192; Client version: 1.4.10056-2503.3).
- The exact steps you are taking to reproduce the error.
- Screenshots of the error message.
- The fact that it's happening in multiple environments.
- The secondary issue with the filter greying out.
Reporting the issue will make Microsoft aware of the problem and prioritize a fix in a future update.

Potential Workarounds (Limited and Not Ideal):
- Filter by objectid (GUID): If you know the specific GUID of the user record you are looking for, you might be able to filter directly on the objectid (the actual unique identifier). However, this is not user-friendly as you typically wouldn't know the GUID.
- Export Audit Logs: As a temporary workaround, you could potentially export the audit logs to Excel and then filter and search for the user within the exported data. This is cumbersome for frequent use.
- Alternative Audit Views (If Available): Explore if there are any other audit-related views available in the Power Platform Admin Center or within Dynamics 365 itself that might allow you to search for user access logs without encountering this specific error. However, the Audit Summary View is usually the most direct for this purpose.
- Wait for a Patch: Ultimately, the most reliable solution will likely be a patch or update from Microsoft that resolves this bug. Keep an eye on release notes and announcements.

Secondary Item (Filter Greying Out): This behavior is also likely a bug related to the update. It indicates an issue with the UI state management after a failed filter operation. This should also be reported to Microsoft Support.

In summary, you have likely encountered a bug in the 2025 Wave 1 update for Dynamics 365 that is preventing proper filtering on the "Record" column in the Audit Summary View. The most important step is to report this issue to Microsoft Support so they can address it in a future release. In the meantime, the suggested workarounds are limited and not ideal for regular use.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak