Did you override the method "cangobatch" and return true? If not, try that.
The index merely lets AX know which layer to get code from, not which parent class to use. I do not think this has anything to do with the correct generation of the .aoi file. On 5/15/07, tabish sarwar <[EMAIL PROTECTED]> wrote: > > Hi, > I am facing a problem with the index management in the Dynaimcs AX 4.0 . > The > case i found is: > I have created a class extending Runbase , i build my program and do what > ever need accordingly , then i change the parent class to RunBasebatch . > When i debug my program now i observed that its still going in the Runbase > constructor rahter than Runbasebatch. means its not updating the relative > index in the aoi file properly . i checked the same scenario with a > seperate > implementation of inheritance and reproduced the same problem . > > The problem persists unless i refresh the AOD manually or delet the aoi > file > and rebuild it again. > > I am unable to understand why the index are not managed properly by the > Dynamics AX itself and why do i need to refresh or rebuild them manually? > > When these index in aoi files are updated . What significance do they have > . > Can any one please explain the case and behaviour of these index (.aoi) > file. > > Thanks in advance. > > Regards, > Muhammad Tabish Sarwar. > > [Non-text portions of this message have been removed] > > > [Non-text portions of this message have been removed]
