Release 144
Release Date: MAY 27th, 2022
ParityFactory Office Manager
Enhancements
- File attachments are now saved to disk instead of in the database, so that database (and application) performance isn’t negatively impacted by referencing large files
- You can now bulk move any selected on-hand inventory/tracked items to another location to allow users to easily fix inventory organization without manually scanning every case
- You now have visibility to original ordered quantities from Archived Shipments so that you can reference them against what was actually shipped
- There is now a higher scale factor limitation when creating Production Runs from Sales Orders using Recipes
- The Estimated Cost button on Production Runs is now hidden by default to reduce implementation confusion
- You can now enter a Note in Create Production Runs from Recipe, so that it’s easier to identify/choose the Production Run number on the Mobile application
- The Create Production Run from Recipe(s) feature defaults to fields based on your chosen Workflow Stage’s workflow preference so that you can create Production Runs faster and more accurately
- The planned issue amounts on an active Production Run scale based on Recipe if you change the planned produce amounts
- You can now change the Expected Output Units and/or Fill on product by product basis for Create Production Run from Multiple Recipes
- One-click tracing now indicates when the underlying tracing data table has not been run
- You can now optionally disable notifications
Bug Fixes
- The Lot Tracing suite no longer shows a blank page upon “Start Trace”
- An unhandled SQL Error is no longer returned to you when trying to adjust an item that was received on an unarchived transfer receipt
- Cycle Counts no longer mis-associates Parent Lot with Child items when scanning the Parent Lot of a mixed container
- Receipts created through API no longer use the Default Location instead of the Receiving Location Preference Property
- Archiving Shipments no longer creates an error
- Unproduce no longer stores ICTransactions with the wrong sign on Display Units/Fill/Net Weight
- The Details action on Shipping Order Products no longer crashes the application
- Fixed several BTB insert scripts that had the call to recreate the table removed, which caused them to grow infinitely
- Archiving Shipment no longer creates unnecessary Bill of Lading toast notifications
ParityFactory Mobile/Handhelds
Enhancements
- There are no longer failures caused by sending IDs with special characters in the URL path
- You can now scan pallet labels during a cycle count and have “child” tracking numbers counted
- You can now print a tracking number label for all items staged or loaded to a shipment
Bug Fixes
- There are no more intermittent deadlocks when Allocating
- Quick split when loading a shipment no longer results in a “Tracking # is required” error
- Scales assigned to other Production Lines once again enable the Get Weight button when Allow Many Production Lines option is enabled
- Production Issue Find Menu no longer suggests tracking numbers with no inventory
ParityFactory API
Enhancements
- There is now a standardized license check and error message across all platforms (Office, Mobile, CMII)
- There is now a single endpoint for the AutoCount process for Cycle Counts
Bug Fixes
- When creating a Bill of Lading PDF, a permissions issue error is no longer thrown
ParityFactory Grading
Enhancements
- You can now view a Processor’s grower statement & crop year settings
- A warning now appears if test results fall outside the defined payment date ranges
- You can now automatically import data from PF Office via API requests
- You can now select multiple varieties
- You can now set the order of test values to be entered
- Alternate Pool Pricing is now supported
Bug Fixes
- You can now create the same Variety for two different Processors
ParityFactory CatchManager II
Bug Fixes
- ACH fields are no longer missing from the payment detail view
- The payment date is now correctly updated for ACH payments
Integrations
Netsuite
Enhancements
- You can now customize the field to import “Ship To Addressee” from NetSuite to ParityFactory
- Returns (Customer and Vendor) are now natively supported to reduce the need for custom NetSuite Suiteapp scripting
- The “Work Order Close Out” transaction now runs on a set schedule
- The “Shipment as a Transfer Order Out” transaction now marks Transfer Orders as fulfilled in NetSuite when complete
Bug Fixes
- Production Out for Issue/Produce is now checking for active status of Production Adjustment Out
- PXJobRecurring metadata is no longer missing for “Transfer Order As” type transactions
- Multi Work Order In transaction is no longer improperly rolling back Production Runs on an update
- Purchase Order In transaction is no longer imported as a Receiving Order in ‘Closed’ status
Microsoft NAV
Enhancements
- Sales Order In transaction can now identify the Customer by the “Sell To No.”
Bug Fixes
- Customer uniqueness by Account name for Sales Order In transaction now succeeds
Quickbooks Enterprise
Bug Fixes
-
- “Object reference Error” in Inventory Out transaction no longer happens when exporting Production
Quickbooks Online
Bug Fixes
- In transaction processes can now retrieve more than 1000 records
Sage 100
Enhancements
- The assigned workflow on a Shipment now persists when the Sales Order is reimported
- A simplified Bill of Materials can now be exported
- Transfer Shipments can now be exported as a single transaction
- ParityFactory-sourced archived Production Run comments now append to existing Sage100 comments, and not replace them
Bug Fixes
- The Transfer Out Schedule Trigger existed, but didn’t actually have a recurring job. This is now fixed.