Month: March 2024

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.

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 Development section is use the OData V4 IN operator in web service queries.

Integrators can now use OData IN operator when querying Business Central web services. This can simplify OData queries and therefore make integrations easier to develop.

Enabled for: Users by admins, makers, or analysts
Public Preview: Apr 2024
General Availability: Apr 2024

Feature Details

Prior to this release, a developer who wanted to query an OData endpoint—for example, to query an API for a (short) list of Customer numbers—would have to write a filter expression such as $filter=CustomerNo eq '10000' or CustomerNo eq '20000' or CustomerNo eq '30000'.

With this release, they can just write $filter=CustomerNo IN ('10000','20000','30000') by using the OData IN operator.

My Opinion

I’m not a developer anymore, but I approve of this type of change which allows for simplified syntax.

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 Development section is write flexible and performant code with NumberSequences.

Improvements to NumberSequences date type streamline the development and execution of code that creates and manages number sequences in the database, resulting in increased efficiency and speed.

Enabled for: Users by admins, makers, or analysts
Public Preview: Apr 2024
General Availability: Apr 2024

Feature Details

This release offers the following improvements to the NumberSequences data type:

• New Restart operation
  Prior to this release, a number sequence had to be deleted and recreated to restart it. Now, a new Restart operation simplifies and speeds up this process. The operation has the following syntax:

  Restart(name: text; seed: BigInteger; CompanySpecific: bool)

• New RangeStart operation
  A new RangeStart operation allows developers to request multiple values from the number sequence at once, meaning no gaps, and fewer SQL round-trips. The operation has the following syntax:

  RangeStart : = Range(name: text; count: integer; CompanySpecific: bool);

• Improved Next, Current, and Exists operations
  These operations are now 8 to 32 percent faster.