# Getting macro issues when trying to update dbt version

**URL:** <https://discourse.getdbt.com/t/getting-macro-issues-when-trying-to-update-dbt-version/11472>\
**Category:** Help\
**Tags:** bigquery, macros, dbt-core\
**Created:** [January 9, 2024, 3:49pm UTC](https://discourse.getdbt.com/t/getting-macro-issues-when-trying-to-update-dbt-version/11472 "2024-01-09T15:49:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fpiklerbr](https://avatars.discourse-cdn.com/v4/letter/f/c4cdca/32.png) [@fpiklerbr](https://discourse.getdbt.com/u/fpiklerbr)\
**Post date:** [January 9, 2024, 3:49pm UTC](https://discourse.getdbt.com/t/getting-macro-issues-when-trying-to-update-dbt-version/11472/1 "2024-01-09T15:49:03Z")

</div>

Hey guys, hope you’re all doing well!  
I’m trying to update my dbt-core version from 0.19.0 to 1.7.2. I have a running project with 700+ models on it. To do this, i’m defining a new docker image with necessary packages and newer versions. This image will be uploaded to AWS and everything will run on ECS.  
While trying to update the docker image locally first, i’m getting some errors when trying to run any command.  
I managed to successfully update dbt and python and all deps, and my dbt debug shows no errors. this is the output:

15:43:16 Running with dbt=1.7.2  
15:43:16 dbt version: 1.7.2  
15:43:16 python version: 3.9.18  
15:43:16 python path: /usr/local/bin/python  
15:43:16 os info: Linux-5.15.133.1-microsoft-standard-WSL2-x86\_64-with-glibc2.36  
15:43:16 Using profiles dir at /sg-dbt/config  
15:43:16 Using profiles.yml file at /sg-dbt/config/profiles.yml  
15:43:16 Using dbt\_project.yml file at /sg-dbt/dbt\_project.yml  
15:43:16 adapter type: bigquery  
15:43:16 adapter version: 1.7.2  
15:43:16 Configuration:  
15:43:16 profiles.yml file [OK found and valid]  
15:43:16 dbt\_project.yml file [OK found and valid]  
15:43:16 Required dependencies:  
15:43:16 - git [OK found]

15:43:16 Connection:  
15:43:16 method: service-account  
15:43:16 database: database  
15:43:16 execution\_project: projext  
15:43:17 schema: fernandop\_dbt  
15:43:17 location: None  
15:43:17 priority: interactive  
15:43:17 maximum\_bytes\_billed: None  
15:43:17 impersonate\_service\_account: None  
15:43:17 job\_retry\_deadline\_seconds: None  
15:43:17 job\_retries: 1  
15:43:17 job\_creation\_timeout\_seconds: None  
15:43:17 job\_execution\_timeout\_seconds: 300  
15:43:17 keyfile: config/bq\_service\_account.json  
15:43:17 timeout\_seconds: 300  
15:43:17 refresh\_token: None  
15:43:17 client\_id: None  
15:43:17 token\_uri: None  
15:43:17 dataproc\_region: None  
15:43:17 dataproc\_cluster\_name: None  
15:43:17 gcs\_bucket: None  
15:43:17 dataproc\_batch: None  
15:43:17 Registered adapter: bigquery=1.7.2  
15:43:18 Connection test: [OK connection ok]

those are my packages:

packages:

- package: “dbt-labs/dbt\_utils”  
version: 1.1.1
- package: elementary-data/elementary  
version: 0.13.2

To test, i’m trying to run a dummy model with a specific macro as I think macro sytax is what’s breaking the runs. I have a macro which uses adapter\_dispatch defined like this:

{%- macro access\_array\_element(col\_name, index) -%}  
{{adapter.dispatch(‘access\_array\_element’)(col\_name, index)}}  
{%- endmacro -%}

{%- macro default\_\_access\_array\_element(col\_name, index) -%}

{{col\_name}}[{{index}}]

{%- endmacro -%}

{%- macro bigquery\_\_access\_array\_element(col\_name, index) -%}

{{col\_name}}[ORDINAL({{index}})]

{%- endmacro -%}

and this is my dummy model, named test\_access\_array\_element.sql

– test\_access\_array\_element.sql

with test\_data as (  
select ‘[“apple”, “banana”, “cherry”]’::json as fruit\_array  
)

select  
{{ access\_array\_element(‘fruit\_array’, 2) }} as second\_fruit  
from test\_data

this is the output i get from running dbt run --select test\_access\_array\_element

root@a67160438635:/sg-dbt# dbt run --select test\_access\_array\_element  
15:27:59 Running with dbt=1.7.2  
15:28:00 Registered adapter: bigquery=1.7.2  
15:28:00 Unable to do partial parsing because saved manifest not found. Starting full parse.  
15:28:03 Encountered an error:  
‘Name’ object has no attribute ‘value’  
15:28:03 Traceback (most recent call last):  
File “/usr/local/lib/python3.9/site-packages/dbt/cli/requires.py”, line 90, in wrapper  
result, success = func(\*args, \*\*kwargs)  
File “/usr/local/lib/python3.9/site-packages/dbt/cli/requires.py”, line 75, in wrapper  
return func(\*args, \*\*kwargs)  
File “/usr/local/lib/python3.9/site-packages/dbt/cli/requires.py”, line 168, in wrapper  
return func(\*args, \*\*kwargs)  
File “/usr/local/lib/python3.9/site-packages/dbt/cli/requires.py”, line 197, in wrapper  
return func(\*args, \*\*kwargs)  
File “/usr/local/lib/python3.9/site-packages/dbt/cli/requires.py”, line 244, in wrapper  
return func(\*args, \*\*kwargs)  
File “/usr/local/lib/python3.9/site-packages/dbt/cli/requires.py”, line 271, in wrapper  
manifest = ManifestLoader.get\_full\_manifest(  
File “/usr/local/lib/python3.9/site-packages/dbt/parser/manifest.py”, line 318, in get\_full\_manifest  
manifest = loader.load()  
File “/usr/local/lib/python3.9/site-packages/dbt/parser/manifest.py”, line 443, in load  
self.load\_and\_parse\_macros(project\_parser\_files)  
File “/usr/local/lib/python3.9/site-packages/dbt/parser/manifest.py”, line 634, in load\_and\_parse\_macros  
self.macro\_depends\_on()  
File “/usr/local/lib/python3.9/site-packages/dbt/parser/manifest.py”, line 728, in macro\_depends\_on  
possible\_macro\_calls = statically\_extract\_macro\_calls(  
File “/usr/local/lib/python3.9/site-packages/dbt/clients/jinja\_static.py”, line 43, in statically\_extract\_macro\_calls  
ad\_macro\_calls = statically\_parse\_adapter\_dispatch(  
File “/usr/local/lib/python3.9/site-packages/dbt/clients/jinja\_static.py”, line 97, in statically\_parse\_adapter\_dispatch  
func\_name = func\_call.args[0].value  
AttributeError: ‘Name’ object has no attribute ‘value’

does anyone knows if jinja syntax is drastically different from one ver to the other? the project has LOTS of macros defined and creating it from scratch is not an option as the team is way smaller than it used to be. also all developers involved in the creation of this 0.19 dbt env aren’t on the company anymore.

Thanks for any answers!