![]() |
VOOZH | about |
The CData Cmdlets Module for Cvent is a standard PowerShell module offering straightforward integration with Cvent. Below, you will find examples of using our Cvent Cmdlets with native PowerShell cmdlets.
Before you can authenticate to Cvent, you must create a workspace and an OAuth application.
To create a workspace:
| event/attendees:read | event/attendees:write | event/contacts:read |
| event/contacts:write | event/custom-fields:read | event/custom-fields:write |
| event/events:read | event/events:write | event/sessions:delete |
| event/sessions:read | event/sessions:write | event/speakers:delete |
| event/speakers:read | event/speakers:write | budget/budget-items:read |
| budget/budget-items:write | exhibitor/exhibitors:read | exhibitor/exhibitors:write |
| survey/surveys:read | survey/surveys:write |
After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.
After creating an OAuth application, set the following connection properties to connect to Cvent:
$conn = Connect-Cvent -OAuthClientId "$OAuthClientId" -OAuthClientSecret "$OAuthClientSecret" -InitiateOAuth "$InitiateOAuth"
Follow the steps below to retrieve data from the Events table and pipe the result into to a CSV file:
Select-Cvent -Connection $conn -Table Events | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myEventsData.csv -NoTypeInformation
You will notice that we piped the results from Select-Cvent 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" in the result set, and we do not necessarily want that information in our CSV file.
The Connection, Table, and Columns are appended to the results in order to facilitate piping results from one of the CData Cmdlets directly into another one.The following line deletes any records that match the criteria:
Select-Cvent -Connection $conn -Table Events -Where "Virtual = true" | Remove-Cvent
The cmdlets make data transformation easy as well as data cleansing. The following example loads data from a CSV file into Cvent, checking first whether a record already exists and needs to be updated instead of inserted.
Import-Csv -Path C:\MyEventsUpdates.csv | %{
$record = Select-Cvent -Connection $Cvent -Table Events -Where ("Id = `'"+$_.Id+"`'")
if($record){
Update-Cvent -Connection $cvent -Table Events -Columns ("Id","Title") -Values ($_.Id, $_.Title) -Where ("Id = `'"+$_.Id+"`'")
}else{
Add-Cvent -Connection $cvent -Table Events -Columns ("Id","Title") -Values ($_.Id, $_.Title)
}
}
As always, our goal is to simplify the way you connect to data. With cmdlets users can install a data module, set the connection properties, and start building. Download Cmdlets and start working with your data in PowerShell today!
Download a free trial of the Cvent Cmdlets to get started:
Download NowLearn more:
👁 Cvent IconAn easy-to-use set of PowerShell Cmdlets offering real-time access to Cvent. The Cmdlets allow users to easily read, write, update, and delete live data - just like working with SQL server.