Tip: If the external link is a fully formed URL, use triple (3) parentheses. Ex: (((TrackingURL)))If you need URL encoding, use double (2) parentheses: Ex: https://www.google.com/search?q=((TrackingNbr))The former is useful if you use multiple carriers (e.g. UPS, FedEx, USPS) where the URL convention is different depending on the carrier.
@fionabruce Yes, it requires a customization. But a DeviceHub connected scale should work for Production Orders or PO Receipts.I needed a similar customization as described by @Gabriel Michaud. My company ships within Acumatica, but we don’t use Automated Warehouse Operations for pick/pack/ship. I was able to add a “Get Weight” action button to the Packages tab/grid of the Shipment Entry screen and have it use a Device Hub connected scale (e.g. Mettler Toledo PS60.) I’ve pasted the code below for anyone who wants a head-start.If Acumatica would add support to DeviceHub for dimensioners... then I'd have something. We have 12 packaging lines and our box sizes are variable, so we are hand-keying W,L,H for every box. It's error prone.Note: DeviceHub uses an API connection for scales, which appear to stay logged-in. I'm assuming this is for each connected scale. We have 15+ scales and several other connected applications which also rely on API connections (e.g. e-commerce, analytics, etc.)I
Has anyone had luck with this?We have 12 packaging lines and 80% of our shipments do NOT use preset boxes, so we manually enter the dimensions of the box for every shipment. This is time consuming and error prone.We'd like to use dimensioners (e.g. Cubiscan or Mettler-Toledo). From what I can tell, DeviceHub works for weight only, not W x L x H. The SMScale DB table validates this assumption; there is only a column for LastWeight. I have some ability to customize Acumatica, but if DeviceHub won't send the dimensions, any customization is a non-starter.Any ideas how to get a dimensioner to work with Acumatica? Cubiscan and Mettler-Toledo units are USB HID protocol compatible... can DeviceHub be upgraded to support dimensions in addition to weight for connected scales?
Doh! That worked. Thanks for the tip @markusray17
Thanks! Note the Workflow/Customization Project Editor value seems to override whatever value is set via SetConnotation() in code. I had to first remove the Connotation value from the Workflow Editor.
Ideally, I need to show only lots which are necessary to replenish the quantity in the primary location. I'll take a look at the InLotSerialStatus table. Having access to the ReceiptDate may be all I need to make this work.Here's a screenshot of a report I've started. I need to populate the ??? in the leftmost column. The Location ID under the triangle is the Primary Location ID. The ??? is where a restocker should go to find more inventory (with FIFO being a factor, when applicable.)You're right. I need to also consider that there might be multiple lots that need to move from potentially multiple locations.Step 1 is getting my restockers pointed in the right direction. Thanks for the tip about [InLotSerialStatus].[ReceiptDate].
Just what I was looking for. Thanks!
Sorry for the confusion. It’s okay to have the warning message for reprints. I like this feature.I would like to hide/show the Print Labels button in the toolbar based on a conditional. Think of it this way...If the labels haven't yet been printed, show the button in the top toolbar. If the labels have already been printed, show the Print Labels action only in the More (...) menu and hide it from the top toolbar. Our warehouse has 10 packing stations and I'm trying to streamline the workflow for our packers.See attached screenshot.
We have the same problem. I would also welcome an option to defer the search until specific parameters were completed. As a workaround, I sometimes default a field (e.g. InventoryID) to a lesser-used value so it will limit the returned data set on initial load.
I'm an Acumatica customer in the B2C retail/ecommerce space. We've used Acumatica's Non-Stock Kits since 2017R2 for build-to-order bundled items, but I've never felt like this was fully baked. I cannot recommend it. We continue to struggle with non-stock kits in Acumatica today. We use stock kits instead of the manufacturing edition for basic assemblies that aren't build-to-order. We've been able to integrate our website with non-stock kits, but there are still big problems in Acumatica with regards to: Availability calculations Purchase forecasting Serialization of NSK components Shipment package contents Landed cost/margin calculations on non-stock kits I would be very receptive to a better solution for BTO (build to order) items in native Acumatica.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.