Hi,
Nice to meet you all. Long time reader first time poster.
In 2022R1, I am trying to publish a customisation that includes an extension to the SOOrderEntry graph. I am having problems though because an existing customisation that also includes an extension to the same graph is already published. The first time I tried this, the whole application crashed because my extension was the only one published, and the other customisation had other code that tried to obtain a reference to its extension using CreateInstance<SOOrderEntry>.GetExtension<”extension name”>().
I tried to replicate this error in a local instance also running 2022R1, but it didn’t happen, and browsing my filesystem provides a clue as to why. In the <Appfolder>\App_Code\Caches folder, my extension is contained in a file named ‘SOOrderEntry.cs’. The other extension is contained in a file named ‘<Package name>.SOOrderEntry.cs’, where <Package name> is the name of the .NET package it exists in. This seems to allow both extensions to coexist, and through testing, I have determined that the code for both extensions is being run.
This implies that there is some system setting that governs whether extensions can coexist like this. Does anybody know of such a setting?
Thanks in advance,
Ben.
Best answer by Zoltan Febert
View original