Account Structures - AX 7 Limit 7?

(0) Share

Report

Posted on by Community Member

We have a test environment and are working to set up and test general ledger etc. When putting in the account structures in AX 7 I get an error/waning that I can't have more than 7 values in the dimension field. Has anyone else run into this and what sort of workaround is there. We have many!!!! more values in each of the dimension/segment fields.

Sam

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (0)

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Sam,

You mean that you can enter only 7 values in a custom financial dimension?

What about other (automatic) financial Dimension values that you use such as e.g. customer, vendor, item, department, etc.

Do these financial dimensions also only hold 7 values?

Have you already tried deleting your usage data and/or refreshed the page?

Ludwig

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ludwig,

Yes, we have six custom dimensions and I have tried in about 3 of them. When I try to leave screen it won't let me because of the errors. I have tried multiple custom dimensions and the answer is the same in all. The main account segment doesn't pose a problem because I don't have over 7 there in a list. Many more accounts but only a could of ranges. We really don't have any data to speak of in this instance. there might be the odd ball transaction but not many.

Sam

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ah, you won the prize, you found the reason it's named AX7. Following thread.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,170 Super User 2025 Season 2 on at

Like (0)

Report

Hi Sam,

Can you provide screenshots of the errors and provide some more background information? I'm not able to understand what exactly is your problem at this moment. E.g. what screen are you leaving?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Wasn't real descriptive, was it. Anyway, some screen shots. Menu area was General Ledger > Chart of Accounts > Configure Account Structures

Notice how I put in eight values in asuDim1 Segment. That is what is causing the error.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,170 Super User 2025 Season 2 on at

Like (0)

Report

Hi Sam,

Unfortunately the screenshot is not visible.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Sam I can't see the screen shot either, please try again.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Andre and Sarah, thanks for the feedback on the picture. Of course, when I went to the page I could see it fine. I will try again.

Menu area was General Ledger > Chart of Accounts > Configure Account Structures

Notice how I put in eight values in asuDim1 Segment. That is what is causing the error.

The message reads: "Only seven allowed value details can be entered for this segment and row. Reenter the 1234;2234;3234;4234;5234;6234;7234;8234 criteria so that the row and segment has no more than seven."

I changed the dimension names and values for confidentiality.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Sam Kerr,

Have you tried setting up the first line more than once with other dim1 critieria,

such as e.g.

10000..29999 1234; 2234; 3234; 4234; 5234; 6234;

10000..29999 7234; 8234; etc

Ludwig

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ludwig,

Thanks for your reply. Yep, and I can get it to accept that. The problem is I don't know how AX would handle this. Lets say you have 49 values for dim1, 49 for dm2 etc all the way up to six dimensions. Would I be faced with a permutation problem of 49x49x49x49x49x49; dim2 valid with all values of dim1 an so forth. Or just 7 rows with all the values for all six dimensions not considering what values are on each row. Hope this make sense, trying to illustrate I don't know, have testing I would have to do. We weren't faced with this issue in AX 2012. This has caught me by surprise. Before I look at completely revamping the entire table I wanted to make sure that this was really the case or something else I didn't know.

Sam

Was this reply helpful? Yes No