Best Of

Hi @Jeffsnake & @AlexaFerrer, how did you go with this?

There could be one of a few things happening:

When you look at the 'Lineage' of your dataset, and you click on the dataflow that is highlighted in Orange, it should mention under the name/heading of your dataflow the reason for this needing your attention (i.e. Field "xxxx" does not exist).

It could also be that there is a temporary server issue during data processing (i.e. Many dataflows are updating at the same time or an external issue on Domo side).

Another thing to check is, in 'Accounts', whether one of the account credentials used to pull your data is showing the attention symbol. If so, you would need to reconnect your account (i.e. Re-Authentication on the platform/app side).

Hi @user048760, how did you go with this? What was the issue/error more specifically that you encountered around joining?

I've used an email forwarding setup with the Google Ads data pull in the past, and the reports I used needed to be built so that the primary key was clear and identifiable before I start any work in Domo. That way, joining and cleaning data steps were easier to carry out.

Hi @danidiaz, how did you go with this?

There's a recent article that sheds some light on how to set up a Snowflake Federated Connector [https://domohelp.domo.com/hc/en-us/articles/360049429094-Snowflake-Federated-Data-Setup] and mentions that "You can create Cards using Analyzer from this [Federated] DataSet, but ETL, SQL DataFlows and DataSet Alerts are not available to operate on Federated DataSets."

If you are after something more specific, to address a business problem/scenario, then it's worth bringing up in the Dojo along with some anonymised/sample data, so that we can help.

Hi @nbrx, in your connector settings, have you tried using the 'Custom Insights' report and searching in 'Columns' for "Post Saves" or similarly names fields?