| Data Services |
Data Queries |
Usage is calculated based on the number of records
processed.
The count of records processed depends on the structure of a query as well as
other related factors such as the total number of records in the objects being
queried.
|
Data queries are used by the data library to retrieve information from the
search index. |
| Data Services |
Intelligent Processing |
Usage is calculated based on the amount of
unstructured data that is processed using AI-assisted features such as LLM-based parsing,
LLM-based visual data preprocessing, image processing, Enriched Indexing, and Intelligent
Context. |
This usage type applies when Intelligent Context is enabled for your data
library. Intelligent Context is on by default for all new data libraries and for all
file-based data libraries created before July 6, 2026. For data libraries created
after July 6, 2026, this usage type applies only if you enable Intelligent Context.
Usage depends on the amount and complexity of data in your uploaded files. See Use Uploaded Files. |
| Data Services |
Unstructured Data Processed |
Usage is calculated based on the amount
of unstructured data that is processed without using AI assisted content processing and
extraction. For example, if the search index processes 100 PDF documents that are 1 MB each,
usage is calculated as 100 MB. If the search index processes five audio/video files that are
on average 100MB each, usage is calculated as 500MB.
In Data 360, unstructured data may
be chunked and vectorized using an embedding model. Usage is computed only once across both
these activities. For example, if one 100 MB PDF document is chunked and vectorized, usage
is computed as 100 MB, not as 200MB.
If you create a search index that uses a data
model object (DMO) as a data source and select Text data type fields from the DMO, all
strings from those fields are indexed and the sum total of all bytes processed is reported
as Unstructured Data Processed.
|
When you set up a Knowledge-based data library, it uses unstructured
data processing to build your search index.
Prior to Intelligent Context, all files were processed via the
unstructured data processing pipeline.
|
| Flex Credits |
Data 360 Queries |
Usage is calculated based on the number of records processed.
The count of records processed depends on the structure of a query as well as other
related factors such as the total number of records in the objects being queried.
When an object is queried in the context of a data space, the number of rows processed is
based on the total number of processed rows in the source object, not the number of rows
pertaining to the particular data space
|
The Answer Questions with Knowledge action or a custom built action use the
Agentforce Data Library to query the index and retrieve relevant information from the
database. The extracted information corresponds to processed rows. |
| Flex Credits |
Intelligent Processing |
Usage is calculated based on the
amount of unstructured data that is processed using AI-assisted features such as LLM-based
parsing, LLM-based visual data preprocessing, image processing, Enriched Indexing, and
Intelligent Context. |
This usage type applies when Intelligent Context is enabled for your data
library. Intelligent Context is on by default for all new data libraries and for all
file-based data libraries created before July 6, 2026. For data libraries created
after July 6, 2026, this usage type applies only if you enable Intelligent Context.
Usage depends on the amount and complexity of data in your uploaded files. See Use Uploaded Files. |
| Flex Credits |
Unstructured Processing |
Usage is calculated based on the amount of unstructured data that is processed
without using AI assisted content processing and extraction. For example, if the search
index processes 100 PDF documents that are 1 MB each, usage is calculated as 100 MB. If the
search index processes five audio/video files that are on average 100MB each, usage is
calculated as 500MB.
In Data Cloud, unstructured data may be chunked and vectorized
using an embedding model. Usage is computed only once across both these activities. For
example, if one 100 MB PDF document is chunked and vectorized, usage is computed as 100 MB,
not as 200MB.If you create a search index that uses a data model object (DMO) as a data
source and select Text data type fields from the DMO, all strings from those fields are
indexed and the sum total of all bytes processed is reported as Unstructured Data
Processed.
|
When you set up a Knowledge-based data library, it uses unstructured
data processing to build your search index.
Prior to Intelligent Context, all files were processed via the
unstructured data processing pipeline.
|
