#Tableau Prep5 debatiendo

Hi 

I think Tableau Prep Builder works this way. 

I tried it. On a PC with Prep Builder 2025.2.4, I ran the 2025.2.5 installer. In other words, I upgraded it. The repository location went back to the default. 

Next, on a PC with Tableau Desktop 2026.1.2, I ran the 2026.1.3 installer. When I started 2026.1.3, it used the same repository as 2026.1.2. 

The Tableau help page says, “When you upgrade to a new release version of Tableau Desktop, bookmarks, workbooks, and data sources that you were working with (that is, that are in the local Tableau repository on your computer) are still available in the new version.” So I think Desktop keeps the repository, but Prep Builder does not. 

I don’t know a way to keep the repository location in Prep Builder. 

@友希絵 福島

はじめまして！ 

同じようなエラーについての相談を見かけたので、参考になりそうな情報を共有させていただきますね。 

「リモートコンテンツに関連する不明なエラーが検出されました（500）」というメッセージの後に、「UNSUPPORTED_API_VERSION」という表示が続くケースが報告されています。 

これは、Salesforce側が受け付けていない古いAPIバージョンで接続しようとしたときに起きるエラーのようです。 

Tableauでも既知の不具合として登録されていましたが、Tableau Prep 2026.2.1のリリースノートで「解決済み」となっていました。 

■チェックしてみてほしいこと

1. Tableau Prep Builderのバージョン
2. エラーの詳細やログの確認

■対処法 

上記のAPIバージョンが原因だとしたら、Tableau Prep Builderを最新バージョンにアップデートすれば直ると思うので、もう一度接続を試してみてください！ 

もし、最新版にしても解決しないときは、Salesforce側の設定も併せて確認してみるとよいかと。 

接続しているユーザーのプロファイルや権限セットで「APIの有効化」がオフになってたり、組織で接続アプリケーションの利用が制限されているかもしれないので。。 

参考になりましたら幸いです！

Hi @Kate Sales

You are correct,  

This error usually comes up when one or more columns going into the Union have different data types, even though there hasn’t been any change to the database schema. 

I’d first check the inputs right before the Union and compare the column names and data types. I’d mainly look at date and numeric fields, as well as any fields that might contain NULLs. 

If you find a mismatch, try explicitly converting the fields to the same type before the Union, for example: 

DATE → DATE
INTEGER → INTEGER
STRING → STRING

Since the flow was working fine before, I’d also try refreshing the input metadata/schema and then checking the Union again. Sometimes the metadata gets stale, or an upstream field starts being interpreted differently, which can cause this error. 

Thankyou! 

You can do the Union in your first Custom SQL script itself as shown below 

SELECT A,B,C 

FROM XYZ 

WHERE Condition1  

UNION ALL 

SELECT A,B,C 

FROM XYZ 

WHERE Condition2 

UNION ALL 

SELECT A,B,C 

FROM XYZ 

WHERE Condition3  

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)