Category: Dynamics

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 1.

The 8th of the new functionality in the Governance and administration section is Control partner access per environment.

Business Central customers with multiple environments are often working with many partners to support each environment. With this feature, customer administrators can now easily and efficiently control partner access to environments. This feature simplifies partner management by allowing administrators to assign partner tenants to each environment.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: –
General Availability: Apr 2024

Feature Details

In 2024 release wave 1, Microsoft are introducing new environment settings in the Business Central admin center that enable internal administrators to control which environments delegated users and multitenant apps from partner tenants can access and administer. Internal administrators can specify the tenant IDs of partners that should be able to access each environment. Delegated users and multitenant apps accessing or administering the environment must belong to an allowlisted tenant. This feature is optional, and if no tenants are allowlisted for an environment, delegated users and multitenant apps will be able to access and administer the environment as they did before. This feature only affects the use of the admin center API by multitenant apps that have been authorized within the admin center

My Opinion

This sounds like a double edged sword; good for users to have the ability to restrict access to environments, but also too easy for something to be set incorrectly and deprive necessary access. However, the same can be said of any security on a system, so I’d say this is a good enhancement. Some of the clients I’ve worked with in the past have had very locked down systems, so they’d like this for witholding access to production while giving access to dev, QA and UAT environments. It could also be useful for companies operating in multiple countries by allowing only the partner for a specific country to access an environment.

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 1.

The 7th of the new functionality in the Governance and administration section is view and filter users with additional user details.

Additional user details and technical data helps administrators be more effective when they handle user requests and resolve issues..

Enabled for: Users, automatically
Public Preview: Mar 2024
General Availability: Apr 2024

Feature Details

You can view additional details about users on the Users page by choosing the Show more details action.

The Users details page offers multiple views that administrators can filter. For example, an administrator might want to view all users with a Microsoft 365 license, or users who are assigned to the SUPER permission set.

Continue reading “New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: View and Filter Users With Additional User Details”

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 1.

The 6th of the new functionality in the Governance and administration section is copy companies with Dataverse integration safely.

Administrators in small or medium-sized companies often wear multiple hats and do many different tasks. It’s important that you can efficiently and safely copy companies if you integrate with Dataverse or Dynamics 365 Sales, reducing the risk of data inconsistencies and saving you valuable time. This enhancement streamlines your workflow so you can focus on strategic tasks, driving your business forward.

Enabled for: Users, automatically
Public Preview: Mar 2024
General Availability: Apr 2024

Feature Details

When an administrator copies companies in an environment that has Dataverse or Dynamics 365 Sales integration enabled, Business Central clears the following settings while copying to the target company:

• Dataverse and Dynamics Connection Settings to ensure that integration correctly re-initiates in the target company.
• Integration records to ensure that the target company doesn’t point to records that are coupled in the source company.
• Integration synchronization jobs to stop synchronization background jobs.
• Integration synchronization errors to clean synchronization errors, it they exist, because they point to errors in source company and would just be considered noise in the target company.

My Opinion

This sounds like a very welcome enhancement as the current process is open to quite a bit of risk. Clearng these settings will help prevent environments syncing incorrectly.

I was doing a project to implement Microsoft Dynamics 365 Business Central with a client recently. When they were doing some UAT they were getting an error when trying to preview or post an assembly order.

I tried the same process on my demo/test environment and did not get the same error as the we were seeing in the client environment. The error they were seeing was this one:

Document No. must have a value in Item Journal Line: Journal Template Name=, Journal Batch Name=, Line No. =0. It cannot be zero or empty

Continue reading “Error Preview or Posting Assembly Order in Microsoft Dynamics 365 Business Central: “Document No. must have a value in Item Journal Line…””

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2024 Wave 1.

The 8th of the new functionality in the Development section is define extension objects in same app as their base object.

By allowing the segmentation of objects into base functionality and extended functionality, it becomes possible to define extensions to objects in the same app as the object itself. This provides an option to group related functionality in smaller contributions and makes it easier to later move these to a separate app as part of refactoring.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Apr 2024
General Availability: Apr 2024

Feature Details

With this new feature, it’s possible to define both the base object and extension objects in the same app. For instance, a table and a table extension can be defined within the same app.

In metadata, extension objects remain separate, as before, so each extension object still requires its own object ID in the used range. The key change is that they can now reside in the same extension/app as the base object. In the case of tables, table extensions that reside in the same app as the base table will be merged into that table in the database schema—resulting in no companion table extension.

This feature is applicable to all extensible object types; for example, page, table, report, enum, and permission set objects.

The capability is enabled by default when targeting runtime version 13.0.