Cvent V2 Connector > Mappings for Cvent V2 > Cvent V2 sources in mappings
  

Cvent V2 sources in mappings

To read data from Cvent, configure a Cvent object as the Source transformation in a mapping.
Specify the name and description of the Cvent source.
The following table describes the source properties that you can configure for a Cvent source:
Property
Description
Connection
Name of the Cvent V2 source connection.
You can select an existing connection or create a new connection. You can also click New Parameter to define a parameter for the source connection.
Operation
An operation to represent a Cvent Rest API.
Each operation is equivalent to a Cvent REST API. When you select a particular operation, Data Integration generates the corresponding request and response fields.
The following table describes the advanced source property that you can configure in a Source transformation:
Property
Description
Cache Size for Web Service Request (KB)
Memory available for the web service request, in kilobytes.
Default is 1024 KB. If the request is more than 1024 KB, you can increase the cache size.
Tracing Level
Sets the amount of detail that appears in the log file.
Select one of the following options:
  • - Terse
  • - Normal
  • - Verbose Initialization
  • - Verbose Data
Default is Normal.
Optimize Transformation
Select to improve performance for processing records at run time.
Default is disabled.

Configuring a request using request message editor

When you create a Source transformation, configure a request message for the operation that you want to perform in the web service application.
Use the Request Message Editor to create a request message. You can use the sample request message for the operation and then customize the request message to specify the data that you want to enter into the data flow.
To customize your request, copy the request message from the sample template to the Request Message Editor pane where you can edit the message and add the attributes for the request. Remove unnecessary and empty tags from the request message to avoid operation failure.
Header fields, path parameters, and query parameters appear as fields in source and midstream transformations.