Skip to main content
Solved

Stock Item Package Dimensions


Hi All,

Is there a way to add item dimensions in Acumatica besides creating attributes? I know there is a volume option on the packaging tab but I want LxWxD.

 

Regards,

Abbas

Best answer by Brian Stevens

I don’t work with API’s, so I’m not completely sure.  I do know that all my custom screens/DAC’s show full WSDL descriptions and can be accessed via the mobile app without any modification to endpoints.

Even if you have to add the endpoints, I still think adding a custom fields is the better route.  Bastardizing the cross-reference (or any field for that matter) is an approach I became very proficient with on a legacy system.  Dedicated fields used for their intended purpose makes for much better data integrity.  If you make 3 fields (L/W/D) then you can set the values to be integer or decimal to reduce typos and control formatting when you display the values on a report.  You can mandate all 3 fields be entered if any field is entered and do math like UPS does in adding all 3 dims to determine if the package is considered oversize.

View original
Did this topic help you find an answer to your question?

6 replies

Forum|alt.badge.img+1
  • Semi-Pro II
  • 88 replies
  • July 20, 2021

@abbas56  You can add attributes.

 

 


Forum|alt.badge.img+5
  • Jr Varsity II
  • 237 replies
  • July 20, 2021

Outside of creating attributes I think the only other route would be a customization that adds custom fields for the dimensions. 


  • Author
  • Freshman I
  • 4 replies
  • July 23, 2021

@larryly Thank you for your suggestion. Already know this one. Was hoping for some builtin fields.


Forum|alt.badge.img+4

Preferred - Personally, I’d add custom fields via a customization project so they are right on the Packaging Tab.

Not recommended, but can work - If you insist on doing it without customization, you could get creative with notes, add to the Body field (Description tab) if you aren’t using that already, or find some other field to repurpose.  If you need it easy to add to a report when defined, you could add as a cross-reference on the item.  I added arbitrarily as a Barcode type on 2 different items using identical values, and it saved it.

 


Forum|alt.badge.img+1
  • Semi-Pro II
  • 88 replies
  • July 26, 2021

@brianstevens  It’s a good idea that add dimensions to cross-reference.    I have another question for you, if I add custom fields and want to use them with OpenAPI. Do I need to define them in the endpoint? I don’t have chance to work on this situation. Just curious.


Forum|alt.badge.img+4

I don’t work with API’s, so I’m not completely sure.  I do know that all my custom screens/DAC’s show full WSDL descriptions and can be accessed via the mobile app without any modification to endpoints.

Even if you have to add the endpoints, I still think adding a custom fields is the better route.  Bastardizing the cross-reference (or any field for that matter) is an approach I became very proficient with on a legacy system.  Dedicated fields used for their intended purpose makes for much better data integrity.  If you make 3 fields (L/W/D) then you can set the values to be integer or decimal to reduce typos and control formatting when you display the values on a report.  You can mandate all 3 fields be entered if any field is entered and do math like UPS does in adding all 3 dims to determine if the package is considered oversize.


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