Forum Discussion
LaszloM
3 years agoQrew Trainee
Thank's for posting this!
I had real trouble finding my workaround: replacing spaces with underscores in the original field label.
Reading through this thread I understand the problem is Pipelines is not putting together a correct JINJA syntax just assumes the field labels do not contain spaces...
In fact I have found this in the QB documentation:
Well, Mike, THX anyway!
------------------------------
Laszlo M
------------------------------
I had real trouble finding my workaround: replacing spaces with underscores in the original field label.
Reading through this thread I understand the problem is Pipelines is not putting together a correct JINJA syntax just assumes the field labels do not contain spaces...
In fact I have found this in the QB documentation:
Example - workaround for address fields with spaces
Address fields in Quickbase using the ‘parent’ label have the safe field name applied when creating the keys for address sub-fields in the pipelines schema. This means that any time a you try to access a sub-field of an address field that contains spaces in the name, the jinja expressions become invalid due to the spaces, or may get interpreted as a jinja expression that differs from the user’s intent.
To work with this behavior in a jinja expression, we suggest you follow these guidelines:
Properties of objects in jinja can be accessed either with the formats of {{a.my_field}}
or through {{a['my_field']}}
, which supports spaces in the property name.
Well, Mike, THX anyway!
------------------------------
Laszlo M
------------------------------