#Tableau Prep22 人がディスカッション中

This can be done by creating the below calculation, using LOOKUP() function:For now, both July and August are in the view just so you can see that July's data for Quantity now lives in August's 'date', as shown above.  But, we don't want to have to select two month's data at a time and yet, two month's of data MUST be in the view. somehow. 

So, we then change the Order Date filter that you originally had into again, a Relative Date filter, again displaying only most recent two months, as I did before:

Then, the question remains, how to show just the current month, but only with last month's data in the current month.  Again, another filter.  BTW, both of these are Table Calculations, so certain fields must be in the view somewhere in order for them to all function correctly and display correctly.  The new calculation will now filter the above result to only the last row in the view:

As to it being automatic and adjusting for next month, it should based on the Relative Date filter..it would automatically adjust to September and pick up August's data. And so on. 

If this response answered your question, please mark it as an Accepted Answer? 

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

I have implemented the solution for day and week. Check the updated workbook attached.

@Jes Hunsballe

not sure yet about it being a bug.   

There is a Refresh 'button' that I'd use to first update the underlying data in Tableau Prep, then I'd step into the Output Step or for that matter the Pivot Step to ensure the data reflects the changes, go forward from there.  But no, you shouldn't have to remove then add the column to make that happen.

If that's not the case, and you're continuing to see the issue after refreshing, then I'd consider opening a support case with Tableau. 

If this response answered your question, please mark it as an

This way, others searching for similar solutions will find the answer faster in the future.

Best, Don Wise (Tableau Ambassador)

@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