I have a similar problem.... But in my case the method that is "renamed_" is a custom method created in the bus layer on a standard object On my Dev env. it's fine, so I stop my AOS and copy the bus layer file to the TEST env. but when restarting the TEST AOS i still get the "renamed_" method.... so strange (AX 4.0->AX4.0)
--- In [email protected], "Thomas Vogt Poulsen" <t...@...> wrote: > > > Yes, i thought so. > > The only solution is to overwrite the SYS, SYP, GLS, etc. where the > methods are present. > > I just hoped that someone had a better solution, but thanks anyway. > > Thomas > > > --- In [email protected], "Karsten Krabbes" > <kkrab...@g...> wrote: > > > > Hi Thomas, > > > > those renamed.. elements are created when Axapta creates the aoi > > file. It seems when while creating that file Axapta finds a class > or > > method in any layer above the sys or syp withe a different ID or a > > method with a diferent definition (static in 2.5 and not static in > > 3.0 or vice versa). > > When this happens, the layer with the renamed element ist > > corrupted !! > > I didn't find a solution to change the back to the original. It > > seems, the layer is modified now. The only chance you have is to > get > > that layer from a clean installation and start again .... > > > > What you can do to solve the problem: > > 1.) change the method in your environment. > > 2.) copy the layer with the renamed_... element from a clean > > installation to your current installation. > > 3.) start Axapta ... and the renamed_ element should be gone :-) > > > > Br > > Karsten > > --- In [email protected], "Thomas Vogt Poulsen" > > <t...@a...> wrote: > > > > > > > > > I have upgraded an Axapta 2.5 to 3.0 SP3 an of course there are > > > differences in the numberserie functionality, but why is the > > > modulelist method in the class NumberSeqReferences called > > > Renamed_ModuleList in the Sys-layer. > > > > > > How do I handle that since the fixAll method uses ModuleList? > > > > > > Best regards > > > Thomas Poulsen >
