AI, in your work.

From request to code

Microsoft merged PR #11739 into the main branch of BCApps on November 5. It is assigned to the Version 30.0 milestone. Its description carries an AI-generated content warning, so this article also relies on the code to establish scope. Microsoft PR.

The original request sought to select consolidation entries by dimension 4 without rebuilding the request and its authentication. That objective explains the change, but does not demonstrate that every dimension filter is supported. Request #11713.

What extensions can modify

In codeunit 102, Import Consolidation from API, both events receive a new final parameter, `var Filter: Text`. The filter is constructed before the event and subsequently used in the request. Change diff.

The standard request and two different counts

If `IsHandled` remains false, execution continues through the standard path, which uses Bearer authentication. Retrieval retains `dimensionSetLines` and uses the modified filter for both the pagination count and result pages.

The closing-date count serves another purpose: detecting entries on that date as part of an accounting validation. It is not the imported total. This distinction comes from reading the code, not from a runtime test. Code at the commit.

The API also sets limits

The `generalLedgerEntry` reference documents properties such as `accountNumber` and `postingDate`, plus the `dimensionSetLines` relationship. It does not document a direct `shortcutDimension4Code` property. Including dimensions through `$expand` does not establish that the parent entry can be filtered by any dimension. generalLedgerEntry resource.

Microsoft also states that its OData APIs do not support lambda operators and that filter expressions using them are ignored. An expression using `any` over dimensions therefore cannot be presented as a verified solution. OData limitations.

Synthetic example: selecting a department

Suppose a company wants to consolidate only the NORTH department, represented by its fourth dimension. This is a functional example from Nexo, not a verified configuration or result.

Before writing the subscriber, the team would need to establish how the endpoint exposes that value and whether it supports the required predicate. It should then check included and excluded entries, pagination and closing-date behavior. Consistency means applying the same business rule where appropriate; it does not require queries serving different purposes to return the same number.

Our interpretation: access to the filter reduces the need to replace the entire request. Its practical value still depends on a valid selection and tests showing which data actually enters consolidation.

Availability: merged into the repository

The 30.0 milestone is a planning reference, not deployment confirmation. The sources reviewed establish neither a released build containing the change nor its activation in a tenant. Before adoption, teams will need to check the installed application's symbols and test the extension in a test environment. PR status.