# powerGate v22

## v22.0.1

`20-09-2022`

**Features**

- A [Connection Error Dialog](<erp_integrations:errors>) informs Vault users about erroneous web requests, responses and their exact cause
- Similarly, in the [BOM Window](<bom_window:errors>), BOMs, rows and Items are automatically marked with an [Error status](</bom_window/status/>) when connection problems occur during Check or Transfer operations
- [powerEvents Restriction events](<inv:powerevents#code_reference/objects/event_mappings>) are automatically restricted when ERP connection problems occur

**General**

- [](</code_reference/net_library/webrequestexception>) provides following properties:
  - `Source` informs about where the issue occurred. This can be either the local computer, powerGateServer or the ERP system
  - `StackTrace` provides details about the actual error occured in powerGateServer Plugins or on the web server of the ERP system

- Connection problems are displayed more clearly on all workstations when beeing caused by:
  - the local computer if no request can be send to the server (e.g. no internet connection available, proxy blocks access...) or if the [license has expired](<activation_and_trial_limitations:stand alone licensing>)
  - [expired powerGateServer licenses](<inv:powergateserver#activation_and_trial_limitations>) (requires [powerGateServer v21.0.5](<inv:powergateserver#change_logs/powergateserver_v21:v21.0.5>) or later)
  - the powerGateServer or the ERP system when no response is returned (e.g. server not responding in time, powerGateServer service not running...)
  - incorrect data input by the Vault user or the ERP integration (e.g. invalid credentials, execution of operations for non-existing entities, bad syntax in requests...) causing the server to respond with [4xx client errors](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes)
  - the powerGateServer or the ERP system while processing `$metadata` requests
- All Cmdlets now respond to non-terminating errors by additionally displaying the error messages in PowerShell consoles before the execution continues (common parameter *[-ErrorAction:Continue](<https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_commonparameters#-erroraction>)*)
- Improved performance of [ERP Entity- and Media cmdlets](</code_reference/commandlets/>) by reducing unnecessary `$metadata` requests to unavailable *Catalog Service*-services ([powerGateServer](<inv:powergateserver#plugins/sample_plugins:catalogservice>) and SAP systems).\
   An attempt to first find the passed *-EntitySet* or *-EntityType* only within previously available services is performed.

**Fixed**

- Issue with [](</code_reference/commandlets/connect-erp>) and [IErpClient.ConnectErp](</code_reference/net_library/erpclient>) which did not fail with [WebRequestExceptions](</code_reference/net_library/webrequestexception>) on failed connections to *Catalog Services* ([powerGateServer](<inv:powergateserver#plugins/sample_plugins:catalogservice>) and SAP systems)
- Follow-up errors after failed or missing [](</code_reference/commandlets/connect-erp>) cmdlet calls in all [ERP Entity- and Media cmdlets](</code_reference/commandlets/>) which terminated with the unclear error message *"No EntitySet found with the given name: ..."* 
- Issue with [](</code_reference/commandlets/get-erpobject>) and [](</code_reference/commandlets/get-erpobjects>) which failed when *-Expand* and *-Select* argument were used together on same navgation property
- Typo in the error message of [](</code_reference/commandlets/new-erpobject>) when multiple entity types match the passed *-EntityType* parameter