After your schema is created in Data 360, you can add source fields to the
data stream as needed. When you add a field to an object in a connected Salesforce CRM org, make
sure that the correct permissions are set for the field.
Required Editions
Available in: Lightning Experience
To add permissions, see Enable Object and Field Permissions to Access
Salesforce CRM in Data 360. For Amazon S3 or Google Cloud Storage
(GCS) data streams, you can add source fields either manually or after they’re discovered by Data 360. Data 360 notifies you when newly discovered fields
are available in your S3 or GCS files to add to your data stream. Records start showing values
for the new source fields from the point in time when the fields are added to the data stream.
From the data stream details page, click Add Source Fields.
For GCS or S3 data streams, select Add Fields Manually or
Add Discovered Fields.
If you're adding the fields manually, enter the file name to pull the source schema from,
and click Verify. The file name must match the file in your
directory.
Data 360 processes the file and shows the list of source fields that are
in the file.
Select the fields that you want Data 360 to add to the source schema.
Tip For Auto Discovered Fields, the Field Last Detected column lets you know when
Data 360 last detected the field in your data source. This information can help
you determine if a field has relevant data to add to your data stream. Use this information to
make sure you’re adding the desired field to your data stream.
Review the suggested data type for each field carefully. You can’t change the data type
after the field is added to the schema. If the suggested data type is incorrect, you can
override it.
Click Save.
The new source fields are added to your data stream’s source schema. If a data stream
refresh fails due to a missing field, disable the field.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
