Feed

This issue is likely to arise when the name or structure of the original fields that your calculated field depends on has changed in the updated version of the data source, or if there was a problem with how the data source was replaced.

Solutions

First, checking for changes in the data source structure is the most crucial step.

• Verify if there are any changes between the new and old data sources in the name, data type, and the table name (if multiple tables are joined) of the underlying fields that your calculated field references.
• If field names have changed, it is highly likely that this is the root cause of the problem.

Correctly Use "Replace Data Source" in Tableau Desktop

The most common way to update the connection without recreating the entire workbook is to use the "Replace Data Source" feature. 

Hello @José Armando de Sousa Aguiar are you looking inside the setup menu displayed when you click on the cog icon (Edit page and Edit object, according on the page on which you were, when clicking) ? See below :Eric

I finally found out what happened to me and what worked for me. 

I was reusing the playground and the free

from a previous training module. It worked for this training module's first unit "Welcome to Coral Cloud Resorts" and was able to make it complete. But when you get to the next unit "Help a Guest Out of a Soggy Situation", you will actually be missing the necessary agent. 

The solution is, follow the exact instruction from the unit "Welcome to Coral Cloud Resorts", create a new playground and register a new 

Hi , 

Please check this article. 

Hello @Adrian Mendoza

you are probably trying to import again, in Creation mode, the data that you have already imported. As the external ID is set up to be unique, it will only allow you, once imported, to update the records, based on the record's external id., but you will not be allowed to create them again with the same external id values. 

Eric

@Sienna Grimm

You're right that scheduled flows only give you Once, Daily, or Weekly. There's no native yearly option. But there are two ways to work around this, and both are pretty clean.

Option 1: Run it daily with a date condition 

Schedule the flow to run daily, but add a condition at the start that checks whether today is the specific date you want. The flow runs every day but only does anything on that one day each year.

The condition to add is a formula check like this:

DAY(TODAY()) = 1 && MONTH(TODAY()) = 4

That example fires on April 1st. Change the day and month values to whatever date you need. Every other day of the year the flow finds no matching records and exits immediately, so there's no real overhead.

Option 2: Formula field on a record to gate entry (cleaner for record-based flows)

Create a checkbox formula field on whichever object the flow runs against, with the same date logic as above. Then set that field as the entry condition for your scheduled flow. The flow runs daily but only picks up records on the one day that formula returns true.

For your specific case (emailing a report)

Since you're sending an email rather than processing records, Option 1 is the better fit. Set up a daily scheduled flow with no object filter, put the date formula condition as the first decision element, and route the email send action only down the "true" path. Takes about 10 minutes to build.

One thing to keep in mind: DAYOFYEAR(TODAY()) = 1 is an alternative formula if you want January 1st specifically, but the DAY() && MONTH() approach is easier to read and works for any date.