web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Strange behaviour "Product builder" after upgrade to R1 CU5

(0) ShareShare
ReportReport
Posted on by 1,435

Hi everyone,

I have upgraded our test environment to CU5. All works fine. This week I planned to upgrade our production environment when a collegue of mine saw that the productbuilder missed a field.

I checked, and all seemed to be correct. So I thought: let's recompile. When I recompile, trouble begins. It compiles fine: No compile errors were found, only gives an error "subknooppunt bestaat al", which is Dutch and means something like "sub node already exists".

From that moment on, the client language changes back to Dutch (it was English before). Also the product is not compiled.

When I make a new product model, and import the settings of the old product model, it compiles fine without errors. It seems there is a problem with the upgrading of the old cu2 base model.

Anyone has a clue why this strange behaviour happens and how I can resolve it for my first product model?

I am not sure if it is wise to continue with the upgrade of our production environment based on this experience.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Wvduren Profile Picture
    1,435 on at

    Ok, it took me a few hours but I solved the issue. Actually what the error ment was that it found some forms/classes that where already there.

    First I compared the adjusted PBA classes to the sys layer. There was no code added that could explain these problems. Then I removed the USR layer of the PBAex classes. Tried to compile again without success.

    Then I checked the forms: that was it! The product builder generated forms were present in the CUS layer... I removed the two forms PBAex from the CUS layer, removed the classes again, and recompiled in the USR layer: Works like a charm! Also the missing field returned.

    Of course this does not explain the change of language... let's just say that there will be a hotfix somewhere to be found...

    Our upgrade is still a go this Easter!

    Hope it helps someone.

    Kind regards, Willem.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans