If like me you are at times lost floating in the ocean of Ax you will find the Google/Bing search engines extremely useful for answering your doubts. By prepending 'axapta msdn' to the queries (the 'ax' term isn't as good, imho) we can usually jump straight into the API we are looking for. One of the frustrating things with this approach, however, is that you are probably using a different version of Ax than the page that we have landed on. The class structure hasn't changed too much it's true but we have more confidence in reading the correct version of the documentation. Searching for ReportSection for example we could land in any of the following:
My understanding is that AX 2012 is now 'released' and I think it's a pity that we can't just change to a '
aa621385(AX.60)
.aspx' to jump straight into AX 2012 should we want to... A lot of the links I select from Google go straight to Axapta 4.0.
As a final note MSDN has this 'Language Filter' option which is useless as we are all X++ gurus. I wonder if it would be far more useful to be able to select a filter on the Ax version that you work with, where a redirection occurs when we first arrive should the equivalent page exist.
No hay comentarios:
Publicar un comentario