Establishing a Connection
With the CData Cmdlets users can install a data module, set the connection properties, and start scripting. This section provides examples of using our OracleERP Cmdlets with native PowerShell cmdlets, like the CSV import and export cmdlets.
Installing and Connecting
If you have PSGet, installing the cmdlets can be accomplished from the PowerShell Gallery with the following command. You can also obtain a setup from the CData site.
Install-Module OracleERPCmdlets
The following line is then added to your profile, loading the cmdlets on the next session:
Import-Module OracleERPCmdlets;
You can then use the Connect-OracleERP cmdlet to create a connection object that can be passed to other cmdlets:
$conn = Connect-OracleERP -Url "https://abc.oraclecloud.com" -User "user" -Password "password"
Connecting to Oracle Fusion Cloud Financials
You must set the following to authenticate to Oracle Fusion Cloud Financials:
- Url: The Url of the account to connect to. Typically, the URL of your Oracle Cloud service. For example, https://servername.fa.us2.oraclecloud.com.
- User: The username of your account.
- Password: The password of your account.
Retrieving Data
The Select-OracleERP cmdlet provides a native PowerShell interface for retrieving data:
$results = Select-OracleERP -Connection $conn -Table "Invoices" -Columns @("InvoiceId, InvoiceId") -Where "Supplier='Bob'"The Invoke-OracleERP cmdlet provides an SQL interface. This cmdlet can be used to execute an SQL query via the Query parameter.
Piping Cmdlet Output
The cmdlets return row objects to the pipeline one row at a time. The following line exports results to a CSV file:
Select-OracleERP -Connection $conn -Table Invoices -Where "Supplier = 'Bob'" | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myInvoicesData.csv -NoTypeInformation
You will notice that we piped the results from Select-OracleERP into a Select-Object cmdlet and excluded some properties before piping them into an Export-CSV cmdlet. We do this because the CData Cmdlets append Connection, Table, and Columns information onto each row object in the result set, and we do not necessarily want that information in our CSV file.
However, this makes it easy to pipe the output of one cmdlet to another. The following is an example of converting a result set to JSON:
PS C:\> $conn = Connect-OracleERP -Url "https://abc.oraclecloud.com" -User "user" -Password "password" PS C:\> $row = Select-OracleERP -Connection $conn -Table "Invoices" -Columns (InvoiceId, InvoiceId) -Where "Supplier = 'Bob'" | select -first 1 PS C:\> $row | ConvertTo-Json { "Connection": { }, "Table": "Invoices", "Columns": [ ], "InvoiceId": "MyInvoiceId", "InvoiceId": "MyInvoiceId" }