November 20, 2026

Financial Dimension OR Financial Tag, and Why?

Hello, 

Ever since financial tags were introduced, you have probably heard a requirement like this:

“We need to capture one more piece of information on the transaction. Can we add another financial dimension?”

Technically, the answer might be yes. But architecturally, there is a better question:

Does this information really need to be a financial dimension, or should it be a Financial Tag?

With Microsoft's continued investment in Financial Tags, including support across more transactions and additional validation options, this is a design decision worth revisiting.


Here's the practical way I look at it.  Start with the purpose, not the technology. A financial dimension should generally represent part of your organization's financial classification.

Think:

  • Cost Center
  • Department
  • Business Unit
  • Project

Dimensions participate in the financial dimension framework and account structures. Account structures can determine which dimensions are required and which combinations of dimension values are valid for particular main accounts.

While a Financial Tag, on the other hand, is useful when you want additional information attached to the accounting entry without making that information part of your formal ledger account structure.

Think:

  • Payment Reference
  • External System Reference
  • Invoice Reference
  • Purchase Order Reference
  • Serial Number
  • Other transaction-specific identifiers

Microsoft specifically identifies information such as document numbers, payment references and external transaction references as scenarios for Financial Tags.

So now think of question like: Does this value describe how I account for the transaction, or does it provide additional context about the transaction?

If it describes the accounting classification, think Dimension. AND If it provides additional context, think Tag.

A practical example can be, Suppose the business asks to capture these values against an expense transaction:

Requirement

My starting choice

Why

Cost Center

Dimension

Part of financial classification/reporting

Department

Dimension

Part of organizational financial reporting

Business Unit

Dimension

Likely to influence reporting and accounting structure

Payment Reference

Tag

Transaction-specific reference

External System ID

Tag

Useful for tracing/reconciliation, not financial classification

Invoice Reference

Tag

Additional transaction context

 This distinction sounds simple, but it can have a significant impact on solution design.

Financial dimensions are structured. They can participate in account structures, validity rules, required dimension rules and defaulting. Financial Tags aren't part of the account structure.

That is precisely why not every reporting attribute should automatically become a financial dimension. 

So, next time the requirement is “Can we add another financial dimension?”, don't start with the configuration. Start with the purpose.

If the value tells us how to financially classify the transaction, think Dimension. If it tells us something more about the transaction, think Tag.

It is a small design decision, but making it early can keep the financial structure cleaner, reduce unnecessary complexity, and ensure we use the right Dynamics 365 Finance capability for the right purpose.


-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

September 15, 2026

[Solved] Visual Studio 2026 “VSCommonPackage” Error After D365FO 10.0.49 Update

Hello,

With the release of Dynamics 365 Finance & Operations (D365FO) 10.0.49, developers are required to move to the newer Visual Studio 2026 development environment. While the upgrade itself is generally straightforward, some developers may encounter the following warning when launching Visual Studio:

"The 'VSCommonPackage' package did not load correctly."




The VSCommonPackage is a core Visual Studio component responsible for loading common services and functionality used by Visual Studio extensions and development workloads.

Solution: 

1. Close Visual Studio and delete the following folder:
C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\18.0_xxxxx\ComponentModelCache

2. Launch Visual Studio in Safe Mode, Open a command prompt and execute: devenv /safemode

3. Reset Visual Studio Settings, Execute: devenv /resetsettings. This restores the default Visual Studio configuration.


Now try to reopen VS and you should be able to use it without any issue now. 

In case you are still facing issues, worth to check my earlier post on similar error, 

https://www.theaxapta.com/2026/03/solved-vsprojectpackage-package-did-not.html



-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta