Power Pages version 9.5.9.x Release Notes

  • Article

Power Pages version 9.5.9.x is now available. This article describes the bug fixes and updates that are included in this release.

Repaired Functionality

The following list details issues that are resolved/updated in this update.

Accessibility

  • The issue has been resolved to differentiate between selected and non-selected pagination controls in high-contrast Aquatic and Desert modes.
  • The issue has been resolved to ensure a unique identification of checkbox selection in each row within a grid.

Functionality

  • The issue related to Dataverse search failure when a single table is passed in Lucene query filters has been resolved.
  • The issue related to Dataverse search failure when a nested filter on a related table is configured has been resolved.
  • The issue has been resolved to ensure that all configured fields are displayed in the Calendar view control.
  • The issue has been resolved to announce a warning message when the maximum character limit is reached in the PWA app.
  • The issue has been fixed to prevent the display of multiple error messages for a field when multiple characters are entered beyond the limit.
  • Code Components: Issue related to Power Apps grid control loading has been fixed.
  • Support for the "distinct" attribute has been added to fetch XML when using WebAPI.

Library Upgrades

  • Power BI client library has been upgraded to 2.22.3

Potential Breaking Changes

  • WebAPI URL parsing has been made more strict in this release to fix some unwanted behaviors. This can lead to errors in some existing WebAPI implementations which might be working before. These errors will be surfaced with http status 400 and error message would be "Bad Request". Typically these errors would be observed in following conditions:

    • An attribute not available in the entity.
    • Unclosed braces.
    • Missing operands between conditions.

    This list is not exhaustive and there could be more conditions like this. To fix this issue, WebAPI URI syntax will need to be corrected.