You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: customer item code not fetched on selection of the item in the sales order (#17755)
fix: holidays was showing on same date in calendar view (#17753)
fix: Opening accounting entry for stock entry (#17710)
fix: Only show registered customers for GSTR-1 B2B Report (#17719)
fix: payment reconciliation against expense claim (#17728)
fix: warehouse tree view taking lot of time to load
fix: range 4 for ageing filter added in the AP/AR report (#17714)
fix: not able to submit sales invoice for italy
17547: - Filling in 'customer' arg field if not already set and if 'party_name' is available - This will fix the logic during which Pricing Rule is constructing the SQL query to list all Pricing Rules related to an item - The reason to put it in accounts_controller is: -# This is the palce when args are made before making call which will end using Pricing Rule logic, which means we don't have to go all over the place to add the proper arg field -# IMHO, it is clean enough in contrast to the case where that code is added to pricing_rule.py for example, cause doing this exposes Pricing Rule to the knowledge about a field called 'party_name' while a Pricing Rule document doesn't have any