Skip to main content
Question

2024 Upgrade issue. Missing Assmembly reference to InventoryItemExt

  • January 26, 2025
  • 4 replies
  • 59 views

Forum|alt.badge.img

Hi,

 

I have an issue with an upgrade from 2023 to 2024 that I haven’t yet been able to work out.  Have been through the normal process of setting up a local Dev environment, recompiling the code making sure that all references to DLL’s are up to date, etc.  The issue is as follows:

 

  1. When I attempt to publish the recompiled code I get the error: The type or namespace from ‘InventoryItemExt’ does not exist in the namespace PX.Objects.IN:
  1. Also, I noticed that when you choose detect modified files, the file PX.Objects_SO_SOLine_extensions.cs referenced in the error message above also features (I have not see this type of behavior before - and I’m confident I haven’t touched that file)

 

  1.  The references I have in my customisation are shown below:

     

  2. the customisation code does not have InventoryItemExt anywhere, and it compiles no issues.  
  3. In the customisation there is a graph extensions to SOInvoiceEntry, and to get the code to compile I commented out the 3 lines below prefixed //JS:

 

These namespaces weren’t being used in the 2023 version so I don’t think this is significant (?)

 

Any ideas on what might be going on here greatly appreciated.

 

4 replies

Forum|alt.badge.img
  • Author
  • Varsity I
  • 71 replies
  • January 27, 2025

Hi,

 

Further to the above.  I exported the customization out of the local site and published to the Live cloud based site.  No errors here, so must be something to do with my local environment?  Any ideas as to what this might be?

 

Thanks heaps in advance for any help,

 

JOhn.


Forum|alt.badge.img
  • Author
  • Varsity I
  • 71 replies
  • January 27, 2025

Also,  the build #’s of the sites involved in this example are a bit inconsistent.

 

  1. The customisation was  originally compiled for 2023.118.500.8456 and published to a Live site of the same build #
  2. The Live site was subsequently upgraded 2024.114.201.2545, and the customomisation would no longer publish.
  3. Next I exported the customisation out of 2024.114.201.2545 and went through the recompile exercise on a local version of 2024.114.200.2355.
  4. The recompiled customisation from 3 above was then publishedOK to the Live site (being 2024.114.201.2545.

Note, the reason that 2024.114.200.2355 was used is that I don’t currently have access to the install package for 2024.201.2545.

I’m wondering if the difference in build #’s is the source of this issue?  Will repeat the exercise once we do have access to 2024.201.2545.

Does anyone have an expert opinion on the above and how it relates to the issue?

 

Thanks,

JOhn.

 


Nilkanth Dipak
Semi-Pro II
Forum|alt.badge.img+10

Hi ​@JWS539,

Have you checked your SOLine_extensions.cs file? It might contain the InventoryItemExt DAC, which could either be part of the same package or linked with another package.

Sometimes, when you add a DAC from the Customization Editor, it includes the namespace based on your package name. As a result, the InventoryItemExt file may not be in the PX.Objects.IN namespace.

Please check the following:

  1. Verify if the SOLine_extensions.cs file contains the InventoryItemExt DAC within the specified lines (lines 46-55) mentioned in the error.
  2. If the same package does not contain the InventoryItemExt DAC, it may be referenced from another package.

Hope this helps!


  • Freshman II
  • 3 replies
  • January 27, 2025

Hi, 

which do you need?

Which field do you want?

You can try with fully qualified name on DACs

 

Best Regards


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings