Regarding the standard issues caused by Microsoft first-party extensions in Business Central 2024 wave 2 (BC25)

Dynamics 365 Business Central

Hi, Readers.
Today I would like to share three problems in Business Central 2024 wave 2 (BC25) caused by Microsoft first-party extensions. I’ve seen this frequently in the Business Central Forum recently, so in this post, I wanted to share it briefly. (Some of this should have been fixed by the time the post is published)

Unable to personalize and bookmark some pages – PowerBI Reports

From Business Central 2024 wave 2 (BC25), we can use embedded Power BI reports out of the box. This functionality was added in the PowerBI Reports extension. More details: Business Central 2024 wave 2 (BC25.1): Use embedded Power BI reports out of the box (In-client Power BI reports)

User couldn’t personalize or bookmark General Ledger Entries, Bin Contents and some other pages.

“An error occurred while applying personalization changes. Please try again.”

Some Posts in Business Central Forum:

Why does this problem happen? This was discussed in detail in the BC Yammer Group. More details: Link1 and Link2. This is because there are duplicate page names in the BC (in different namespaces), and these pages come from the new extension, PowerBI Reports.
So all issues that manifest it this way coming from conflicting page names (in different namespaces).

Uninstalling the PowerBI Reports extension solves the issue.

Unable to create a new blank customer or vendor – E-Document Core

This is another weird problem. When you create a new customer or vendor, if you do not choose to create from a template, an error will occur when creating a blank record.

No. must have a value in Customer: No.=. It cannot be zero or empty.

No. must have a value in Vendor: No.=. It cannot be zero or empty.

Some Posts in Business Central Forum:

Why? This can be found in Share details -> Copy error details.

Error message:
No. must have a value in Vendor: No.=. It cannot be zero or empty.
AL call stack:
“E-Doc. Vendor Page”(PageExtension 6161).OnAfterGetCurrRecord(Trigger) line 2 – E-Document Core by Microsoft

Yes, this is caused by the E-Document Core extension, which is also a first-party extension from Microsoft.

We can download the symbol file of this extension and debug it briefly.

This is caused by the following code.
pageextension 6163 “E-Doc. Customer Card” extends “Customer Card” -> trigger OnAfterGetCurrRecord() -> Rec.TestField(“No.”);

As for the solution… Create customer and vendor from a template, or uninstall this extension.

Some data is automatically added to the upgraded environment (including production) – Subscription & Recurring Billing

This is a new feature in the 2024 release wave 2 plan.
Manage subscription billing and revenue and expense recognition:

Business value:
Businesses are finding ways to create recurring revenue streams by selling goods and services on a subscription basis. This release lets you manage subscription contracts in Business Central. The new subscription module lets you spend more time selling and less time organizing and invoicing contracts.

Feature details:
Companies across sectors have increased their adoption of digitalization and are revamping their products and services to accommodate subscription-based business models.

https://learn.microsoft.com/en-us/dynamics365/release-plan/2024wave2/smb/dynamics365-business-central/manage-subscription-billing-revenue-expense-recognition?wt.mc_id=DX-MVP-5004336

And this feature is enabled by default for all environments, so when you upgrade the environment, the extension is automatically installed and some data is automatically inserted. Here is some of the data (not all of it).

Dimensions:

No. Series:

Job Queue Entry:

Source Code:

If customers notices this data and needs the partner to delete it, it will be a huge workload……

PS: Mr. Waldo has written a very detailed post on this issue. I suggest you read it directly.
More details: Business Central Fall Cleanup

And Teddy (That NAV Guy) also mentioned this new dimension, you can also refer to his post.
More details: D365 Business Central : CUSTOMERCONTRACT dimension on BC25 Upgrade

One more – Error when installing AppSource extensions with Delegated Admin

In Business Central Forum: Error when installing an App Source App with a delegated Admin User

This was also discussed in detail in the BC Yammer Group. More details: Link

Back in the oooold days (5-6 years ago), the embedded AppSource experience was added to BC to allow delegated admins to install apps in BC, because of the issue of doing so in the online marketplace.

Unfortunately, that embedded AppSource experience stopped being maintained by the AppSource team, and was eventually sunset April 2024, with the ask to use custom inline product experiences on the AppSource apis instead – hence it goes away.

Because we actually do understand that it is common in the channel for delegated admins to install apps on behalf of customers we decided to invest in building our own, new embed experience, based on the AppSource APIs. It cannot do all what the online experience can, but it was built primarily for the admin install scenario.

Thus it is somewhat ironic that the new Microsoft AppSource Apps page blocks installing many apps by delegated admins. The challenge has been that there are different types of AppSource apps, and in the currently available api we do not have enough context to uniquely identify these. We’ve had pretty strong feedback from ISVs who does not want it to be straight-forward to install Contact Me apps, and thus we picked the settings that does not allow that to begin with, but it then includes Get It New (because we cannot see the difference). Apps with plans can be installed. We’ve asked for better apis, and had hoped for this to be fixed for 2024 release wave 2 release, but it has not.

Thus, the only current path right now is to allow installing any app (as delegated admin).

Allow install by SBalslev · Pull Request #2164 · microsoft/BCApps (github.com)

This would then include Contact Me apps, which it so far has not been possible to install in AppSource online or embed. This will surely result in feedback from ISVs with Contact Me apps, as some perceive app install access as a way to enforce licensing, but it has always been possible to install with a direct url, so in reality it will be the same, although easier. Restricting to only delegated admin being able to install these, partly alleviates the issue.

https://www.yammer.com/dynamicsnavdev/threads/2971289036767232

That’s all. So the next question is, how can we avoid this problem in the future?

First of all, we have discussed in Business Central 2024 wave 2 (BC25): Manage environment updates more flexibly – Major update: 30(60) days -> 5-month and Optional minor updates that starting from BC25, the major update period has been extended to 5 month.

This type of standard problem usually only occurs in new major versions, so it is a good choice to update the environment in the last month, provided that the customer is not interested in the new features.

Another option is to uninstall all unused first-party extensions. In Dynamics 365 Business Central: Can we uninstall Microsoft (First-party) extensions and how to install them back?, we’ve discussed that if you don’t need any add-on features, you only need the following three standard extensions. Even if you uninstall a standard extension, you can install it back.

PS: aka.ms/BCYammer: Dynamics 365 Business Central Partner Community (Formerly: Development)
More details: About Business Central partner community on Viva Engage (formerly Yammer)

END

Hope this will help.

Thanks for reading.

ZHU

コメント

Copied title and URL