Released on March 10, 2020
A bug which appeared in betas 7.18 lead to wrong interpretation of fields coming from virtual articles in sets when they are inserted in replacement fields of an estimate.
It always returned the value 0 or blank to the replacement field in the estimate instead of the value of the field defined in the added columns of the database of sets.