Power BI Credentials in Setup and more
Introduced a centralized Power BI credentials section in the Business Portals setup page, aligning it with the existing App Registration configuration. This change removes the need to configure Power BI credentials separately for each portal and ensures a consistent, streamlined setup experience.
Smaller improvements
Description: Introduced a centralized Power BI credentials section in the Business Portals setup page, aligning it with the existing App Registration configuration. This change removes the need to configure Power BI credentials separately for each portal and ensures a consistent, streamlined setup experience.
Impact: Users can now manage Power BI credentials from a single location, reducing configuration effort, minimizing errors, and improving maintainability across multiple portals. This enhancement simplifies administration and supports more efficient onboarding and updates for Power BI integrations.
What To Do
- Power BI credentials will not be fetched automatically from active portals.
- Power BI on existing configuration will not be modified and continue working as is.
Steps to do:
- Enter Business Portals Setup.
- A new section called Power BI Registration will be shown.
- Enter the credentials of Power BI in this section.
The secret will accept the encrypted and unecrypted forms. It will detect and save it automatically in the appropriate format.
Description: Introduced a credential verification feature in the Business Portal that checks whether user credentials and configurations are current and properly synchronized with Business Central, ensuring alignment between the two systems.
Impact: Users can now quickly confirm that their Business Portal access and configurations remain valid and up to date, reducing configuration errors, improving data consistency, and enhancing overall system reliability.
Description: Introduced an intermediate snapshot capability during portal updates, providing an additional backup point to support safer update execution and easier validation.
Impact: Users can now recover more quickly and reliably from failed portal updates, reducing downtime and risk of data loss while improving overall update resilience and maintainability.
Fixed and improved
Description: Resolved an issue where the internal user account "updateimages" was incorrectly displayed as an eligible participant in the ticket system. The visibility logic for this internal account has been adjusted to prevent it from being added as a ticket participant.
Impact: Users will no longer see or be able to select the "updateimages" account as a participant in tickets, improving data integrity and ensuring that internal system accounts are not used in operational workflows.
Description: Resolved an issue where Power BI credentials were not migrated when upgrading a Portal pre-config unify instance from versions earlier than 2.7.x.x to 2.7.x.x or later. The migration process has been updated to ensure Power BI credentials are correctly carried over during upgrades.
Impact: Users upgrading affected portals will now have their Power BI credentials preserved, preventing Power BI configuration failures and ensuring dashboards and reports load as expected after the upgrade.
Description: Resolved an issue where newly created portal users in NAV 2018 could not set an initial password because the password change process required a non‑existent current password. The fix aligns NAV 2018 behavior with the previously implemented correction, allowing initial password creation without requiring a current password.
Impact: Business Portal Administrators can now successfully create users and enable them to set their initial passwords, restoring expected user management functionality and preventing account setup failures for new users.
Description: Resolved an issue in the Business Portals Job Queue where users encountering errors during processing were not being deactivated as intended. The existing fix from the Microsoft Dynamics NAV implementation has been ported to AL to ensure consistent handling of affected users and prevent repeated email notifications caused by unresolved errors.
Impact: Users who trigger errors during Job Queue execution are now correctly deactivated, preventing duplicate or repeated email notifications. This improves system reliability, aligns Business Central behavior with the prior NAV implementation, and reduces noise and confusion from unnecessary email alerts.