[Feature] reconcile the difference in included columns between source <> transform packages

[fivetran-jamie]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

There are a number of fields that we include in staging models but do not persist them in our end models. This makes it difficult to use our passthrough column format to bring in these fields (you need to make aliased-copies of these fields as passthrough columns and then rename them later in model in your own dbt project)

So, for each of these staging-layer-only fields, we should decide to either

1. include the field in the end models the table is joined into, or
2. remove these fields from the staging models so it is more straightforward to use passthrough columns to bring them in

Describe alternatives you've considered

No response

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance and will schedule time during your office hours for guidance.
• No.

Anything else?

No response

[fivetran-jamie]

entity_id in particular has come up as a roadbump that would be resolved here