How does DimensionValues[1]…[n] work on LedgerTrialBalanceTmp.DimensionValues

(2) Share

Report

Posted on by D365Explorer

In the LedgerTrialBalanceTmp table I found the field DimensionValues (EDT = DimensionSetSegmentValue, String Size = 30). Yet in forms and code I see it used like this: DimensionValues[1], DimensionValues[2], etc. I also looked in SQL and found multiple dimension columns in related table.

I’m trying to understand:

1. How this single DimensionValues field can behave like an array of slots (indexed [i]).
2. How the system stores multiple distinct dimension values inside one string field
3. How it then allows access via DimensionValues[1], DimensionValues[2], etc in code.

Regards,

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

Martin Dráb 239,029 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

DimensionSetSegmentValue doesn't represent a single string; it's an array. Expand the ArrayElements node to see that:

If you look at an array field directly in the database , you'll see that there is a separate field for each array element.

1 people found this reply helpful.

Was this reply helpful? Yes No
D365Explorer 97 on at

Like (0)

Report
Copy link

Link copied!

Dear Martin,

Thank you for the response.

I have a few follow-up questions and would appreciate your insights:

1. Given that DimensionSetSegmentValue has a string length of 30, how is it able to store multiple dimension values within such a short length?
2. When I attempted to replicate this in a test table and stored values similar to those shown in the Trial Balance, the SQL table displayed multiple columns.

How can a single string field behave this way dynamically?

Regards,

Was this reply helpful? Yes No
Verified answer

Martin Dráb 239,029 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

1. It's not a single string - it's an array of 12 strings, each of them can hold 30 characters.

2. Your observation confirms what I said before ("If you look at an array field directly in the database , you'll see that there is a separate field for each array element.").

You can't do that at runtime - data types and table fields are defined in the application at design time, and reflected in the database by DB synchronization.

Was this reply helpful? Yes No