#Tableau Prep27 personnes en discutent

@Victor Lagrenaudie​  May I know your Tableau server version? Try below options and see,

1. Clear your browser cache , cookies and try different browser.
2. Ensure web authoring for flows is enabled on your Tableau server.
3. Try creating any simple flow and try edit that and see.
4. Try editing the flow in a different time when server is not busy.
5. Disable any browser extension

If none of the solutions didnt work, then please reach out to Tableau support for additional help.

P.S. If this post resolves the question, would you be so kind to "Select as Best"? This will help other users find the same answer/resolution and help the community keep track of answered questions. Thank you.P

Hi, @Mathias Berg

I’m not sure if this is what you were looking for, but please take a look. 

It seems that before long, Tableau will allow you to link data sources together. 

You can prepare separate data sources for each object and then combine them. 

By splitting up the data processing, you may be able to shorten refresh times. 

Since this is a long‑awaited feature for many users, it’s exciting to see it coming. 

<tableau help> 

https://help.tableau.com/current/pro/desktop/en-us/datasource_extend_compose.htm

This behavior is a known limitation with Tableau Prep + Tableau Cloud when using “Append to Table” with certain connections like SFMC.

Root Cause

• Append / Incremental refresh requires a stable, owned published data source with valid run-as identity
• With SFMC connections: 
  • The connection does not fully persist user context/credentials for append operations
  • Tableau Cloud fails to resolve the run-as user, resulting in: 
    • “No Tableau Server user found”
    • Blank datasource reference
• “Create Table” works because it creates a new datasource each run, avoiding this dependency

Why this happens

• Append requires: 
  • Existing published datasource with consistent owner + embedded credentials
  • Proper connection mapping during flow run
• SFMC connector + embedded credentials often does not support append/incremental reliably in Prep flows

Correct and practical approaches

Option 1 (Recommended):

• Avoid Append
• Use Create Table (full refresh) instead

Option 2:

• Publish the target datasource separately
• Ensure: 
  • Credentials are embedded and valid
  • The datasource owner is explicit and unchanged
• Then reference it in Prep (still may fail due to connector limitation)

Option 3:

• Use an intermediate storage: 
  • Write to Snowflake / DB / Hyper
  • Then handle append from a supported source

Key Conclusion

• This is not a permission issue
• It is a connector + Tableau Cloud limitation with Append/Incremental on SFMC
• Full refresh (Create Table) is the only consistently reliable approach

Bottom line:

Append and incremental refresh with SFMC in Tableau Prep Cloud are

@Matthew Laforest

came across your post trying to discover other ways to increase load time between Salesforce and Tableau Prep. Similar to what Diego shared, the best way I've found to increase load times from Salesforce in Prep is to use the Custom SQL option and query only the fields you need, and filter down in that step. It does use SOQL rather than SQL so there are some limitations there. However, when connecting directly to the Salesforce table in Prep, even if you filter down the input step, it still queries every single row and column despite the filter. Going the Custom SQL route actually does narrow the query down so I've seen much faster load times going that route. 

If you've found any other solutions I would love to hear them if you're willing to share! My super large queries are still taking way too long for my liking so I'm trying to find anything else I can implement for faster loading times.

First, can you confirm that TabPy is actually running and reachable from the Mac? For example, if TabPy is running on the default port (9004), try accessing the endpoint from a browser or using a command such as:

curl http://localhost:9004/status

If that does not return a response, the issue is likely with TabPy itself rather than Tableau Prep.

A few other areas worth checking:

• Verify that Tableau Prep and TabPy are both running natively on the same architecture (Intel vs Apple Silicon), especially if you're using Python environments created on a different platform.
• Confirm that macOS Firewall or security settings are not blocking local connections.
• Check whether Tableau Prep is configured to connect to localhost, 127.0.0.1, or a hostname that resolves correctly on your Mac.
• Review the Tableau Prep logs and TabPy logs for connection-related errors. They often provide more detail than the UI.
• Make sure the TabPy version is supported by the version of Tableau Prep you are using.