Cmdlets
All the following OData cmdlets support OData version v1, v2, v3, v4.
They all try to perform as less server requests as possible, in order to ensure high performance when communicating over the network or the internet with your ERP system.
Connection management
Cmdlets for connection establishment with OData services:
Name |
Description |
---|---|
Connects to an ERP-System. |
|
Disconnects from an ERP-System. |
Cmdlets to read metadata of connected OData services:
Name |
Description |
---|---|
Returns information about the connected services |
|
Returns information about the available entitySets |
|
Returns information about the available EntityTypes. |
Performance
When some of the services are permanently not available, you can speed up your process by disconnecting them.
Please see example Disconnect all not available services.
The following Cmdlets require a successful connection between the current application and the ERP system or powerGateServer.
For them to work properly, all the necessary ERP services (or a single CatalogService) must have been previously connected by the Connect-ERP cmdlet.
Entity transfer
Cmdlets for reading, adding, updating and removing OData entities:
Name |
Description |
---|---|
Returns a specific entity from the ERP-System. |
|
Searches for entities depending on the passed arguments. |
|
Updates an existing entity on the ERP-System. |
|
Creates a new entity and transfers it to a ERP-System. |
|
Deletes a specific entity from the ERP-System. |
|
Returns a new default instance of the desired ERP entity. |
Media exchange
Cmdlets for downloading, uploading and updating OData media files such as images, text files or even Autodesk file formats:
Name |
Description |
---|---|
Uploads media files to the ERP-System. |
|
Downloads media files from the ERP-System. |
|
Updates media files on the ERP-System. |