Quantcast
Viewing all articles
Browse latest Browse all 73760

AOD file is never reduced

Hi AX experts,

 

My company purchased and implemented product builder in Dynamics AX 2009. One product builder id represent one finish good to be sold. If we want to use the product builder, we have to compile the product builder, and in the AOT it becomes a class with this format name : PBAExecutable_%1_%2
where %1 is companyId and %2 is the Product buiilder id (sequence number). When we compile, we must run the ax client with the layer as specified on product builder parameter. 

In the beginning we decided to use usr layer to compile all product builder records. It started three years ago, and by today our usr layer file (usr.aod) has reached size 2.1 GB. I can assure you that it is because of product builder classes. We have 5 entities, and each entity has it's own product builder. By the format name I mentioned above you can imagine how many classes are created in AOT. If one product builder contain BOM, each BOM will be treated as one method.

A few month ago, we had issue with the cus layer file. Somehow we couldn't create any object, even one job. That job is displayed as cup layer but we can't run that job. The more we try, the more cup objects were created. We need to restart the AOS, and after that all the cup objects are gone. 

Since we sell items that need to be configured through product builder, and sometimes we have to change the BOM of the item, system forces us to compile the product builder. But this cup issue won't allow these product builders to be compiled. 

Daily operations must go on. We tried to ask the vendor, no satisfy answer provided. We decided to use another layer that is still available for us, which is USR layer. 

Now the USR layer file increases, and it reaches almost the same with CUS layer. Just a few days ago, the same issue happen again. Everytime object is created in USR layer changed to USP, and we can't compile any object.

Now most of the product builder classes belong to both layer cus and usr layer, because of compilation requirement. We assume that AX 2009 has issue if the aod file reaches size  more than 2GB. So we try to reallocate the classes to be compiled in cus and usr layer. We deleted discontinued product builder, and all unwanted classes are deleted from AOT. But the size of AOD is never reduced..I was wondering, why if create a new object and compiled the file size is increased but when the object is deleted from the AOT the file size is still the same.

At this point, at least we need solution to reduce the file size of AOD. But we couldn't make it.. Product builder is the core of our business. How can we reduce the AOD file? Or if you read the scenario above, what is the right solution for it? 

 

Thanks,

 

Tulus Tobing


Viewing all articles
Browse latest Browse all 73760

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>