Thursday, 23 August 2007

V4 Service pack 2

Just installed this on one of my installations and found much to my consternation that MS has continued to rename tables.

Even in Service Packs !

The Country as it was in V4 and SP1 is now AddressCountryRegion which is consistent with the rest however .....

Anyhow enough said I have not found any others, so far.


Palle commented that as far as he knew the Country had been renamed in V4, and he is right, what happened is that the upgrade process from V3 allowed the object to retain it's old name all the way through to SP2 but no further.

So what I thought was an SP2 issue was in fact an issue related to the upgrade process.


Palle Agermark said...

Hi Sven,

I was quite puzzled when I read your post, because I was the developer changing these names for 4.0 and I distinctively recall that also the Country table was renamed.
I have just checked it and in the AX 4.0 I have, the table is named AddressCountryRegion in the SYS layer.

Best regards,
Palle Agermark

Sven Jochimsen said...

Well maybe I have a strange version of V4 SP1 but I hope not :-).

Maybe the problem is related to the way in wich my upgrade was done from V3. That is the country was modified in a lower layer and thus stayed with it's old name.

More study needed.

Will update

Fran├žois Gobert said...

Thank you for the time you spend sharing your experience in DAX.

Regarding AX SP's, do you know some guidelines we have to follow to maintain our BUS layer in different SP's versions?

Thank you!


Sven Jochimsen said...


In order to help me answer the question correctly I would need to know whether you are a customer or a partner.

As a partner you should be able to resolve the differences in the BUS layer and by launching the upgrade engine in that layer you should have a project with the elements needing work singled out for you.

As a customer you normally do not have acces to developing in the BUS layer, and therefore you have to resolve the issues in the layer you have access to (either USR or CUS usually) and unfortunately the elements you will have to look at individiually as the automated option only works when you are in the layer which needs correcting.

Typically I create a project (empty) and ask the filter mechanism to fill it with all objects in the layer. Switch on the show all objects flag and delete (manually) any objects not in SYP (the patch layer from the SP)
I have a job somewhere doing that in a project (the deletion part)
and then proceed using the comparison tool to ascertain what needs doing.

It sounds longer than it actually winds up being unless the coders in the BUS really dsagreed with the standard code :-)

Hope this helps

Anonymous said...

i've read your old post about unidimensional nature of dax cost accounting. i am now facing a problem of explaining it to my boss, who thinks everything is possible with axapta. as there are very few examples of implementing this, could you please tell me is it possible anyhow to make an allocation or to count a cost rate using two dimensions (to count one cost rate per cc/purpose).
Best regards