Hi folks, I tried dbt-fusion + elementary and. i got dbt1501: Failed to render SQL unknown method: map has no method named update for volume test

data_tests:
          - elementary.volume_anomalies:
              arguments:
                timestamp_column: updated_at
                time_bucket_period: hour
                time_bucket_count: 1

You’re hitting two separate Fusion‑related issues: 1. Wrong argument names for

volume_anomalies

in Fusion syntax. In dbt‑Fusion, Elementary tests must put all test arguments under

arguments

, but the keys themselves stay the same as in the docs. For

volume_anomalies

you should use the nested

time_bucket

structure, not

time_bucket_period

/

time_bucket_count

. [volume anomalies; dbt Fusion OSS] Replace your test with:

data_tests:
     - elementary.volume_anomalies:
         arguments:
           timestamp_column: updated_at
           time_bucket:
             period: hour
             count: 1

2.

map has no method named update

(dbt1501) is a Fusion compatibility issue. This error comes from dbt‑Fusion’s stricter Jinja / mapping behavior and appears when older macro code calls methods that aren’t available on Fusion’s

Map

objects. Elementary’s Fusion support starts at package version 0.20 and requires the new

arguments

/

config

layout. [dbt Fusion OSS] To resolve it, make sure that: ◦ You’re on elementary >= 0.20 in

packages.yml

, then run:

dbt deps
       dbt run --select elementary

◦ All Elementary tests in your project follow the Fusion pattern: ▪︎

arguments:

→ anomaly parameters (e.g.

timestamp_column

,

time_bucket

, etc.). ▪︎

config:

→ dbt config like

severity

,

tags

,

meta

. [dbt Fusion OSS] If, after upgrading to 0.20+ and fixing the YAML as above, you still see the same

map ... update

error, the knowledge sources don’t provide a more specific workaround for that exact method name, so I can’t say more confidently what else is needed beyond upgrading Elementary and using the documented Fusion syntax. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@Dragos Cioata this was fixed in the elementary version that wad released today. It was due to a breaking change in one of the recent dbt-fusion versions.

@Itamar Hartstein thx