Visual MorphXplorer
If anyone else is wondering what the heck happened to this in AX4.0… you aren’t alone. For the longest time I thought I was just missing it, that it had somehow been moved and I just couldn’t find the location.
Most of the tests like 1Y0-456 and EX0-101 were hard to clear since no data was available. With test king, this material can be bought individually as well as in group with 642-845 and 642-825 series.
Well I did some asking around - I wasn’t alone in missing it. It is extremely (in 3.0) handy in tracing out those table relationships when troubleshooting issues. I do not have an official or definitive answer, however I do have some information. My understanding is that it has temporarily been stripped out of AX. Something much better is being worked on… so it is really not there now. (Not just hidden.) The good news is that something will be coming back. I haven’t heard when or what form it will be in, but I was happy to hear that. (Perhaps AX5.0?)
Technorati Tags: Microsoft, Dynamics AX, MBS, AX5.0, Visual MorphXplorer, AX Development




Try the reverse engineering tool in the add-ins. It creates a Visio diagram.
Take a look at 3.0 and examine what parts are needed.
it’s not very dificult to transfer the visual morphXplorer from 3.0 to 4.0
we (www.stz-loerrach.de) done it !
I haven’t tried the add-in tool, so might have to tinker with it sometime. Though as far as porting it goes, really haven’t needed it thaaaat much.
So when I have, I have just loaded 3.0, looked at a relationship, and tested really quick to see if it still worked the same. So far it has, but like I said, my use of it is limited.
Hi
I am new to axapta and I am using 3.0 version
My visual morphxexplorer is not working as I think it should - I can’t see no relations under context menu when I add new table to diagram even if in AOT there are relations.
Please help
Hi Slavek - you need to make sure you have run the cross-reference function.
Tools > Development tools > Cross Reference > Periodic > Update
Now this can take a while, so run it sometime where you can let the job run for a while.