All Collections
New Releases
Known Issues: 5.2.0
Known Issues: 5.2.0
Miles Dinsmore avatar
Written by Miles Dinsmore
Updated over a week ago

This page lists issues and bugs that Ample Organics has identified but has yet to fix as of the version 5.2.0 release in April 2020. Many of these issues will be resolved in subsequent releases.


Ref. Key



CTLS report columns that track "Unpackaged - Pure Intermediates - Quantity Processed" will not populate properly if a Pure Intermediates Bulk Lot is used as an input for a Work Order that has two or more output Bulk Lots of different types. This use case should not come up often, but be advised that until this issue is rectified, each Work Order that use Pure Intermediates as an input should only output to one type of Bulk Lot.


Both the CTLS and CRA reports are currently adding the tote weight on top of Bulk Lot weight when calculating opening and closing inventory values. This is inaccurate, as a tote accounts for a subset of a Bulk Lot's total weight, not an additional source of weight. This is causing inaccurate weight totals.


Ref. Key



A user has the ability to remove an active lab report from a QA Released Bulk Lot. There should be validations to prevent this.


Lab potencies for Extracts-Ingested (discrete) lab reports created before Skunk Haze (5.0.0) and 5.1.0 are not displaying properly on the Overview tab in the SKU Profile when the SKU's potency setting is set to "Display from Lab Report".


If a user does not enter a Sample Volume in a lab report, the Sample Volume column in the report's row on the Lab Reports tab will be blank. A dash should fill that space. This issue only appears in Bulk Lots that use volume as an optional unit of measure.


Ref. Key



In the Add Product to Cart modal in the Orders module, Dried THC Equivalence and Dried CBD Equivalence values are missing from all product types that have their potency result set from the Client Sales Setup tab in the SKU's Profile. This is because these fields don't exist in the Client Sales Setup tab, and the software will have to pull the values from the lab report regardless of the user configured potency setting.

Affected product types are Extracts-Topicals (discrete), Edibles-Solids (non-discrete), Edibles-Solids (discrete), Edibles-Non Solids (non-discrete), Edibles-Non Solids (discrete), and Extracts-Other (non-discrete).


If a SKU's Prescription Deduction field is set to 0 grams, a custom policy's Percentage Discount will instead apply to the entire SKU price, which may result in the SKU's entire price being discounted.


If a user processing an order applies a manual discount (created in the Discounts module), and a policy is applied on top, the two discounts may overlap, and the total discount may exceed the base price of a given item.


If a client completes an order that includes a cannabis SKU with volume fields has a Prescription Deduction set to 0 grams, order related documents are not generated.


If a user tries to place an order with multiple policies applied–one with unlimited coverage and one with limited coverage–and error will be triggered if the order meets the limit of one of the policies.

Combo SKUs

Ref. Key



A user cannot create a Combo SKU that includes an accessory, or a Combo SKU that groups a SKU of the Dried cannabis product subclass with a SKU of another product subclass.


Retail price values for Combo SKUs are displayed as $Infinity/g on the product listing page in the Client Portal. All subclasses except for Dried should display the full price based on what is populated in the Retail Price and Sales Price fields in the Client Sales Setup tab.


Ref. Key



The Received Inventory tab and flow is not yet available in French, German, and Spanish.


The Pick Cases modal should include a "select all" box so that clients don't have to check off potentially hundreds of cases individually when creating a shipment in the Wholesale application.


Ref. Key



The Destruction Report PDFs in previously closed/destroyed Destruction Lots are not displaying data values in the Seeds (#) column. This is because these values are saved when the lot is closed/destroyed, and the PDF did not collect this data prior to version 5.1.0.


Archived SKUs still display in the products listing in both the Client Portal and the Orders module.


In the Products module, a user can move a Packaging Run to any other SKU, regardless of each SKU's product type. This should not be allowed; users should only be allowed to move Packaging Runs between SKUs of the same product type.


The Archive button in a client policy page will be moved to the bottom-left corner.

Did this answer your question?