AI · MICROSOFT · SHARED KNOWLEDGE

AI, in your work.

Understand what’s changing.
Discover what you can do with it.

IN FOCUS / AI & industry

Directions EMEA 2026: preparing for Paris

Dates, registration and AI topics in the announced Paris agenda, with questions and examples for evaluating Business Central solutions.

Read the story 4 min

TRY IT IN NEXO

A useful answer starts before the question.

Choose a task. Compare two requests. Take away a prompt with context.

Open the prompt workshop Interactive example · Fictional data · No signup
FROM IDEA TO NEXT STEP

“Summarise this meeting.”

ContextGoalFormat

“Extract decisions, actions and what still needs confirming.”

The difference is in what you ask.

EXPLORE NEXO

The latest, with perspective.

36 articles

Topic: All

Average costing in BC: a transfer correction to follow

A technical and functional proposal based on an October 28 commit message, focused on the reported scenario, regression design, and unresolved release coverage.

Microsoft · Announcement: · Editorial review

A worker operates a forklift between shelves holding goods in a warehouse.
Warehouse work (archive, 2023). Photo: Ricardo J. Reyes / DVIDS. The appearance of U.S. Department of War (DoW) visual information does not imply or constitute DoW endorsement.
nNexo CommunityEditorial review · 2026-10-28

ANNOUNCEMENT & AVAILABILITY

PR #13220 was merged into main on October 28, 2026. The commit message reports passing regressions in a 28.x environment, while stating that the BCApps port and localized variants have not been built or executed locally. The sources consulted do not confirm distribution to customers.

Fix average cost adjustment overflow on same-period transfers (#13220)

What we know An October 28, 2026, BCApps commit message describes a correction intended to prevent average-cost adjustment overflow on same-period transfers. It explains a condition based on cumulative item quantity before excluding transfer recipients. The message reports passing regressions in a 28.x environment, while explicitly stating that the BCApps port and localized variants have not been built or executed locally.

Proposed angle Prepare a tracking note for inventory consultants and developers. The commit message describes regressions covering negative, zero, and positive balances, checking adjustment completion and conservation of quantities and values. We would propose adapting those scenarios for our own validation. The editorial value would be connecting a functional scenario to regression planning, without presenting the repository change as an already distributed fix.

What remains to verify We have not audited the diff or executed the code. Validation of the port, affected localizations, and the product versions or cumulative updates incorporating it remain unconfirmed. The reference to a 28.x test environment does not establish delivery to customer installations.

Created with AI assistance and reviewed by Nexo Community. Practical proposals and editorial interpretation are distinguished from documented facts.

Read the source ↗

CONNECT THIS IDEA

A useful next step.

AI & industry · 1 minCopilot assisted permissions: deciding what agents can do automaticallyAI & industry · 3 minMicrosoft 365 Copilot offers: preparing purchasing and catalogues for December

More articles appear as you continue scrolling.