Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The Salesforce Bulk Upload function is used to map and push data to Salesforce Objects for handling billing. This function is a processor. The function integrates directly with Salesforce with Bulk API 2.0 v49.

For more information about Bulk API 2.0 v49, see Bulk API 2.0 v49

To use the function, you must have to following knowledge:

The data pushed to Salesforce Objects can be either of the following:

  • Salesforce Usage Object, with or without added custom field mappings
  • Standard or custom objects, using custom field mappings

Configuration

Under OAuth Credentials, enter the the following:

  • Client ID (Consumer Key)
  • Client Secret (Consumer Secret)
  • Username

  • Password

Note!

You can also use the Secrets Wallet toggle button to select a predefined secret from your Secrets Wallet.

Under Object Configuration, select to use Usage object or Other (standard or custom). You can toggle between the two selections at any time.

Note!

Any modifications, that is, adding or removing fields are remembered when toggling between Usage and Other. 

Under Field Mapping, enter the source and target fields. Custom fields can be added as needed.

Under Response Timeout, enter the number of seconds to wait for job completion. The default value is set to 60 seconds.

Note!

After configuring the Salesforce Bulk Upload function, it must be noted that the data initially displayed in the Preview is mock data. Mock data refers to fake data that is displayed to avoid unnecessary usage creation. You must run the stream to produce the actual results.

Example Field Mappings

In the first example, Usage is selected. Select source field from the drop-down menu. The target fields uses the default field names and are greyed out.

Note!

Only the first three fields are mandatory while the next three fields can be removed, using the remove button to the right of the target name. You can manually restore fields if they were removed by mistake, or use another copy of the function and start over. 

The second example shows a simple use of the selection Other (standard or custom). Add fields manually as needed.

As mentioned, the data handled by the function is either usage data objects or custom data objects. In both cases, additional data can be added.

Note!

Incomplete data entries are skipped and are not pushed to Salesforce Objects.

  • No labels