Extend same graph in multiple customisations

Question

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.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 \App_Code\Caches folder, my extension is contained in a file named ‘SOOrderEntry.cs’. The other extension is contained in a file named ‘.SOOrderEntry.cs’, where 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.

Zoltan Febert · Accepted Answer

Hi @benb1977,There is not settings for it, the only rule is the two extensions need to have different names or namespaces.using PX.Data;using PX.Objects.SO;// First customizationnamespace PX.Objects.SO{ public class SOOrderEntryExt : PXGraphExtension { }}// Second customization, same Namespace, different Namenamespace PX.Objects.SO{ public class SOOrderEntryAnotherExt : PXGraphExtension { }}// Third customization, same Name, different Namespace namespace PX.Objects.AnotherNamespace{ public class SOOrderEntryExt : PXGraphExtension { }}

benb1977 · Answer

Thanks @Zoltan Febert.Yeah that’s what I did. I had the classes as defined below but it crashed the server. The other thing that may be a problem is the fact that I’m actually programming on a rebranded Acumatica product called ‘MYOB Advanced’ here in Australia. I didn’t think there would be any difference in the way customisations are coded, but that seems to be the only explanation.// First customisation packagenamespace PX.Objects.SO{ public class SOOrderEntry_Extension : PXGraphExtension { }}// Second customisation packagenamespace PX.Objecs.SO{ public class SOOrderEntry_PopupExtension : PXGraphExtension { }}

Sign up

Social Login

Login to the community

Social Login

Scanning file for viruses.

This file cannot be downloaded