You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the titular macro with this as the default. This is to allow for the case where we wish to append anything to any pass through fields. We ran into this in salesforce where we were joining 1 table twice, and ran into problems with ambiguous columns. The below is Joe's fix for specifying which table a field is coming from.
{% macro custom_persist_pass_through_columns(pass_through_variable, identifier=none, transform='', append_string='') %}
{% if var(pass_through_variable, none) %}
{% for field in var(pass_through_variable) %}
, {{ transform ~ '(' ~ (identifier ~ '.' if identifier else '') ~ (field.alias if field.alias else field.name) ~ ')' }} as {{ field.alias if field.alias else field.name }}{{ append_string }}
{% endfor %}
{% endif %}
{% endmacro %}
The text was updated successfully, but these errors were encountered:
fivetran-joemarkiewicz
changed the title
update_persist_pass_through_columns
[FEATURE] - update_persist_pass_through_columns to include field aliasing
Feb 23, 2024
Update the titular macro with this as the default. This is to allow for the case where we wish to append anything to any pass through fields. We ran into this in salesforce where we were joining 1 table twice, and ran into problems with ambiguous columns. The below is Joe's fix for specifying which table a field is coming from.
The text was updated successfully, but these errors were encountered: