Hello Everyone,
I am currently working on transforming unstructured data such as videos, audio files, and PDFs into structured data so that it can be leveraged in different Salesforce use cases, including Agentforce.
At the moment, I am facing an issue while trying to retrieve records from the UDLO and establish the complete data ingestion flow. My current approach is:
- Connect AWS S3 to Salesforce Data Cloud.
- Create a new UDLO and UDMO using the data from S3.
- Ensure the data is successfully ingested into the UDLO.
The challenge is that although the data appears to be reaching the UDLO, I am unable to retrieve or utilize the records as expected.
If anyone has faced a similar issue or has suggestions, best practices, or relevant resources, I would greatly appreciate your guidance.
Thank you in advance for your help and support.
#Data Cloud
try to check the UDLO→UDMO transform job status in Data Cloud's job monitor. If it's not listed as running/completed, it was never triggered — this is the direct cause of "data reaches UDLO but UDMO stays empty. Resource: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-awss3-udlo.html
The step your build may be missing or need to be enabled : UDLO → UDMO →
Search Index (Easy Setup) → Data Explorer validation. UDLO ingestion and UDMO population are two independently-triggered processes. File-notification wiring (Lambda → connected app → UDLO) only proves the first process. The second — chunking, embedding, and DMO population — is provisioned separately via the Search Index tab, and it's optional at UDLO creation time.
UDLO ingestion and UDMO/Search-Index population are separate, independently-triggered stages, and Job Monitor only reflects jobs actually provisioned.
Let me know, if this is resolved.
