Quantity parsing issue with GS1-128 / UPC-128 barcodes after update

Environment:

<li data-path-to-node=”4,0,0″><strong data-path-to-node=”4,0,0″ data-index-in-node=”0″>Business Central Version:0
<li data-path-to-node=”4,1,0″><strong data-path-to-node=”4,1,0″ data-index-in-node=”0″>Dynamic Ship Version:9.9720.1

<strong data-path-to-node=”5″ data-index-in-node=”0″>Issue Summary:
Since updating to the versions above, Dynamic Ship is no longer correctly applying the Unit of Measure (UOM) quantities when scanning UPC-128 barcodes during packing. This feature worked perfectly prior to the update.
<p data-path-to-node=”6″><strong data-path-to-node=”6″ data-index-in-node=”0″>Example & Steps to Reproduce:
We are scanning a UPC-128 code that contains the case UPC, lot number, expiration date, and quantity. Our scanner is configured to strip the parentheses, outputting the following raw string: 010803310027933710325152811303006</p>
<p data-path-to-node=”7″><em data-path-to-node=”7″ data-index-in-node=”0″>Note: When testing this exact string in the Barcode Rules, it parses perfectly and detects all parameters correctly.

</p>
<p data-path-to-node=”8″>Based on our Item References configured on the product card, this case UPC (08033100279337) corresponds to a <strong data-path-to-node=”8″ data-index-in-node=”109″>quantity of 6.</p>
<p data-path-to-node=”9″><strong data-path-to-node=”9″ data-index-in-node=”0″>Current Behavior (The Bug):</p>

<li data-path-to-node=”10,0,0″><strong data-path-to-node=”10,0,0″ data-index-in-node=”0″>First Scan: Dynamic Ship packs exactly <strong data-path-to-node=”10,0,0″ data-index-in-node=”39″>1 unit instead of the configured case quantity of 6.
<li data-path-to-node=”10,1,0″><strong data-path-to-node=”10,1,0″ data-index-in-node=”0″>Second Scan (of the same barcode): Dynamic Ship now recognizes the case quantity and attempts to pack <strong data-path-to-node=”10,1,0″ data-index-in-node=”102″>6 units. However, because 1 unit was already packed on the first scan, it throws an overpack error (since only 5 units are left to pack). <em data-path-to-node=”10,1,0″ data-index-in-node=”240″>(Note: I have attached a screenshot of this error).

<p data-path-to-node=”11″><strong data-path-to-node=”11″ data-index-in-node=”0″>Troubleshooting Steps Taken:
To isolate the issue, we confirmed the following:</p>

<li data-path-to-node=”12,0,0″><strong data-path-to-node=”12,0,0″ data-index-in-node=”0″>Barcode Rules: The Barcode Rule testing tool parses the 128 string and identifies all values perfectly.
<li data-path-to-node=”12,1,0″><strong data-path-to-node=”12,1,0″ data-index-in-node=”0″>Manual Entry: If we manually type the 14-digit case UPC (08033100279337) directly into the field, Dynamic Ship correctly packs 6 units.
<li data-path-to-node=”12,2,0″><strong data-path-to-node=”12,2,0″ data-index-in-node=”0″>Standard Barcodes: Scanning standard case barcodes (non-UPC-128) processes the correct case quantities without issue.

<p data-path-to-node=”13″><strong data-path-to-node=”13″ data-index-in-node=”0″>Conclusion:
There appears to be a disconnect between the Barcode Rules engine and the Dynamic Ship packing module specifically regarding how it handles Item Reference quantities on the initial scan of a UPC-128 code.</p>
<p data-path-to-node=”14″>Could you please investigate this regression? Let us know if you need any additional logs or setup details.

Thank you</p>