Set up financial dimensions for integrating applications with multiple companies

(0) Share

Report

Posted on by Mariano Gracia

Hi,

I have to import master data into multiples companies through DMF, but I'm concern about default dimension fields, in the form "Set up financial dimensions for integrating applications" I set up the string format for the DefaultDimensionDisplayValue string, but this setup is shared across all companies which, in my opinion, is wrong because my companies use different dimensions structures, so how it is supposed I have to configure it?, I have to add all the dimensions used by my companies?, I now it will work, but it makes the export proces from the other legacy systems (I have multiple systems) more complex, as they have to build the dimensions string according the unique configuration I have in 365, so imagine I have 8 dimensions configured in 365 and in the company A in his legacy system only use 1 dimension, they have to build a string with 1 dimension and 7 blank spaces separated by "-", in AX 2012 I could setup multiple ways to define the default dimension string in the "Source data formats" in the DMF module, because when I add an entity in a processing group I also indicate the source data format which specifies the dimension string format, so I can create one processing group for each company, and each processing group could use the same entities but with different source data formats. Any ideas about it?, or it is the only way to proceed.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Mariano Gracia on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

To make a backing table consumble as a financial dimension to not be shared between companies is fully supported by Dynamics (https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/financial/dimensionable-entities), like CustTable or VendTable, I also did applied it in other customer with AX2012 and I have to say that it is easy and it works perfectly.

Was this reply helpful? Yes No
Suggested answer

ZvikaR 152 on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

Definitely it sounds like a step in the right direction to not create different dimensions in each company.

Messing up with the dimension framework and modifying it to not be shared sounds like quite a risky idea, definitely far removed from best practice.

Was this reply helpful? Yes No
Verified answer

Mariano Gracia on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

After a long time thinking about this problem we have decided not to use a personalized dimension (which shares all dimension values across the companies) but to create a new table and a dimension related to this table, doing this way each company can create his own dimension value (as the table has the property "Save data per company" set to true), they do not share those values across all the others companies and we only need to add this dimension into the "Set up financial dimensions for integrating applications" form instead of adding multiple personalized dimensions for each company.

Was this reply helpful? Yes No
Mariano Gracia on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

Zvika, let's say I work only with 8 dimensions, in dimension "A", the company "B" decides to create the new value "aa", and this new value will be only used by company "B", the answer is yes, it is nearly un-workable as he needs to setup the dimension to be disabled in the other 399 companies, that it is why the customer has decided to create specific dimensions for each company (using account structures), so they won't need never disable dimensions for the other companies. I think most people will agree me.

Was this reply helpful? Yes No
Suggested answer

ZvikaR 152 on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

your example you mention having total of 8 dimensions.

Personally I have not seen a deployment with more than 10 dimensions, and this include sites that have over 400 companies implemented.

Do you consider having to work with configuration with 8 dimensions as un-workable?

I think most people would disagree with you.

Of course, if you feel this is a necessary feature, you can log it in the ideas site

experience.dynamics.com/ideas

Was this reply helpful? Yes No
Mariano Gracia on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

Zvika, as I said in my original post I know that it is a possible (and may be the only one) solution. My customer has more than 50 companies, each on will use different account structures, so to mantain the string to import DefaultDimension is complex, not from the point of view of the 365 but the legacy systems, and as I said before, this issue was not present in AX2012 as I could define multiple ways to import the DefaultDimension string, and now I have only one way to setup the string for importing the values

Was this reply helpful? Yes No
ZvikaR 152 on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

Add to that configuration all dimensions.

When you upload to particular company, you will only populate values for the dimensions that are relevant for that particular company.

This is not only done when having different companies - even within one company different accounts have different dimensions, but the integration set up is still one.

Was this reply helpful? Yes No
Mariano Gracia on at

Like (0)

Report

RE: Set up financial dimensions for integrating applications with multiple companies

I know that, but because the DimensionAttribute shares the values to all companies the customer has decided to create multiples dimensions so he can setup different account structures for each company to avoid what you have explained to me. Anyway, what it is most annoying is that this problem was avoided in AX 2012 because I could define multiple ways to import the string for the DefaulDimension field, somehow it is a step backward.

Was this reply helpful? Yes No