Validation for Customization failing on local env

Hi @ vib1980 

The warning message you receive is not the cause of the validation failing.

Similar to building a solution in VS, your solution will still build with warnings.

Could you please share the customisation package?

Aleks

Hi @aiwan ,

Thanks for the response. I’m not concerned about the warnings it’s just the validation failure that is bothering me. It’s failing for all customizations that I have tried so far. Attaching the test customization.

One more thing to add the same test customization is publishing successfully on 2024r1.

I cannot load it, I’m on 23R2.

Sorry dude!

But if the code isn’t doing anything, I would delete it and try again.

The class name in your code is CompanyMaintExt but the file name shows CompanyMaint_Extension. These should match - either use:
Class name: CompanyMaint_Extension (recommended for consistency with file name)
Or rename the file to match CompanyMaintExt
Add the [PXCacheName] attribute to properly declare the graph extension

Not sure but seems something wrong with the Customization editor in general for 2023r1. Get the following error when trying to open the default workflow for Cases.   

@ vib1980 

could you maybe try the set up a fresh instance?

Aleks

@ vib1980 you are using namespace PX.SM that is used by Acumatica itself.
While I’m not sure that this causes your problem, it’s possible that there is a validation that checks this.
It’s also possible that another graph extension with the same name exists in this namespace.

You should avoid using Acumatica own namespace. It’s similar to how you don’t usually use the System namespace for your own code. Create a unique namespace. A good start will be to avoid the “PX” prefix, almost all Acumatica namespaces start from it.