Released on December 6, 2018
When a request was executed in the macro with the IEstimate.RunQdvRequest method, the request has set some optimizations for ignoring fields that were not used in the request. Those optimizations were not reset when the request finished. This produced an error when the macro tried to get or set a minute field that was not used in the request.
Because a frozen version in an estimate has always and ID of 0 unlike a pushed version where A=1, B=2, etc. attempting to build BI reports on frozen versions resulted in error messages.
Also, when listing all versions to create a BI report, no version was checked when the estimate was frozen.
When centralized storage is used and an article is inserted in the minutes, then of course the article is stored in the database of the estimate but the set depth was 1. This was no real problem but for readability it is now changed to 0.