# powerVault v20

## v20.0.7

`03-07-2019`

**General**

- Improved [Get-VaultFileBom](</code_reference/commandlets/get-vaultfilebom>) performance by not including *Parts Only*, *Structured-Multilevel* components and old versions in any Vault API calls
- Improved [Get-VaultItemAssociations](</code_reference/commandlets/get-vaultitemassociation>) performance by retrieving all files in a single API call

**Fixed**

- [Get-VaultFileBom](</code_reference/commandlets/get-vaultfilebom>) with arguments *-GetChildrenBy* [LatestVersion](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>), [LatestReleasedVersion](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>) and [LatestReleasedVersionOfRevision](<code_reference/commandlets/get-vaultfilebom:bomrowversiontype>) results in following issues:

  > - *VaultServiceErrorException*: *"1013"* for certain BOMs with *Parts Only-* or *Structured-Multilevel-Views* enabled and *purged* or *deleted* components
  > - InvalidOperationException: *"Sequence contains no elements"* for assemblies with Phantoms that got updated with new components that are promoted and merged on higher level
  > - [Bom_Quantity](</code_reference/objects/filebomrow>) of component on higher level is returned when Quantity is overridden, instead returning sum of quantities with all new components that are promoted from a updated Phantom assembly
  > - ArgumentOutOfRangeException: *"Index was out of range"* for assemblies with Phantoms that got updated and have the same Part one time used with type [Normal](<code_reference/commandlets/get-vaultfilebom:remarks>) and one time used with type [Reference](<code_reference/commandlets/get-vaultfilebom:remarks>)

## v20.0.2

`24-05-2019`

- Official Release

**General**

- End User License Agreement (EULA) has changed

## v20.0.1beta

`11-01-2019`

**Features**

- Added support for Vault 2020 (BETA)