Skip to main content
Topics#Data CloudFrage von JEET Patel
JEET Patel fragte in #Data Cloud
29. Sept., 13:12

Data Explorer Query Fails After Creating Data Model - "Table does not exist" Error in Data Cloud

Question:

Hi Community,

I'm experiencing an issue with Salesforce Data Cloud in my Developer Org and would appreciate your help.

Background:

I recently enabled Data Cloud and successfully created multiple data streams using:

  • AWS S3 connectors
  • Other Salesforce orgs
  • File uploads

All data streams were ingesting data correctly into the Data Lake object, and I was able to query the data through the Data Explorer without any issues. 

 

The Problem:

After creating a Data Model for one of the data streams, I can no longer query that data in the Data Explorer. I'm receiving the following error:

Failed to execute query: table "Employee_Salary_Data__dll" does not exist 
[TraceId: 03ee4f5f7bbd2900] 
SQLSTATE: 42P01 
QUERY-ID: MTAuNzYuMTUyLjIxNjo3NDg0_62dbcd6e-8bd0-41ad-9e69-8b3c17b1ed92 
DETAIL: line 1, column 197: ...ion__c" from "Employee_Salary_Data__dll" fetch next 10... ^~~~~~~~~~~~~~~~~~~~~~~~~~~ 
QUERY: select "cdp_sys_SourceVersion__c", "Credit_Card__c", "KQ_UUID__c", "DataSource__c", "DataSourceObject__c", "First_Name__c", "Gender__c", "Bank_Name__c", "Email__c", "InternalOrganization__c" from "Employee_Salary_Data__dll" fetch next 100 rows only

Troubleshooting Steps Already Completed:

  1. ✓ Deleted all data streams and created new ones → Same error persists
  2. ✓ Deleted all data models and data streams, then recreated → Same error occurs
  3. ✓ Logged out and logged back into the org → Issue remains

Environment Details:

  • Org Type: Developer Edition
  • Data Cloud Status: Enabled
  • Data Streams Created: Multiple (AWS S3, Salesforce-to-Salesforce, File Upload)
  • Issue Triggered After: Creating a Data Model

 

My Questions:

  1. Root Cause Analysis:
    • What could be causing the "table does not exist" error after creating a Data Model?
    • Why does the error persist even after deleting and recreating data streams?
    • Could there be a caching or indexing issue in Data Cloud?
  2. Solutions:
    • What are the recommended steps to resolve this issue?
    • Are there any hidden settings or metadata cleanup steps I should perform?
    • Should I try clearing cache or running any diagnostic tools?
  3. Disabling Data Cloud:
    • If I can't resolve this, can I disable or fully delete Data Cloud from my org?
    • Will disabling Data Cloud affect any other Salesforce features?
    • Is there a safe way to remove all Data Cloud components?
  4. Prevention:
    • What's the correct workflow for creating Data Streams and Data Models to avoid this issue in the future?

Additional Context:

  • I didn't modify any security settings or permissions related to Data Cloud
  • I haven't made changes to the data source files
  • The issue occurs across all newly created data streams after the first Data Model creation

Has anyone encountered this issue before? Any suggestions on how to move forward would be greatly appreciated! 

 

I have also attached the Data Stream and Data Explorer screenshots. 

 

Thanks in advance! 

 

#Data Cloud

Data-Stream-page.png
Data-Explorer-page.png
2 Antworten
  1. Venkat Yadav (SFDCINDIA)
    Heute 06:59

    Hi @JEET Patel

     

    This looks more like a  Data Governance access issue than a problem with your Data Stream or Data Model. 

     

    Salesforce has a known scenario where Data Explorer shows: 

     

    table "xxxx__dll" does not exist 

     

    when the user doesn’t have the required Data Governance policy access to that Data Lake Object. 

     

    I would check these first:

    1. Go to Data Cloud / Data 360 → Data Governance → Policies.
    2. Check whether the All Data Access Ruleset policy is available.
    3. Make sure your user is assigned a policy that gives access to the affected DLO, such as Employee_Salary_Data__dll.
    4. After updating the policy, refresh the Data Stream and try Data Explorer again.

    Also check the Data Stream Refresh History and confirm that records are actually being ingested into the DLO without failures. 

     

    I wouldn’t keep deleting and recreating Data Streams at this point, because if the issue is Data Governance access, recreating the DLO will not fix the underlying permission/policy problem. 

     

    Regarding disabling Data Cloud, I would avoid doing that just for this issue. First check the governance policy. If the correct policy is already assigned and the error still continues, then I would raise a Salesforce Support case with the TraceId and Query ID from the error. 

     

    Based on the error you shared, Data Governance policy access would be my first check.

     

    Thank you,

    Venkat Yadav.

Antwort schreiben...
0/9000