Pipeline Incorrect Template Error
I have seen post about this error but I have yet to find anything to help me figure out how to resolve the error with my pipeline.
Validation error: Incorrect template "{{c.related_member}}". Val...
Forum Discussion
It seems that the value "{{c.related_member}}" is expected to be an integer, but it contains the string "related_member" instead.
You may need to check the configuration or data mappings to ensure that the correct field is being used. It's possible that there is a mistake in the configuration that is causing the incorrect value to be passed to the template.
Additionally, make sure that any variables or placeholders in the template are correctly defined and populated with the appropriate values before passing them to the template.
------------------------------
Justin White
------------------------------
Thanks for replying, Justin.
While researching this error, I saw similar explanations. I was confused as to why that is because I am mapping to a text field. Related Member is a text reference field and I am mapping it to a key field that is also a text field (email addresses specifically). As I type this, I wonder if the pipeline is interpreting an integer value because the field being mapped to as a key field, despite the fact that the key field is a text field. If that is the case, how do I get around it. I tried using the simple query and the advance query approach and both lead to the same exact error.
------------------------------
James Carr
------------------------------
No problem, I wish I could help you solve this.
You can try using a formula field in the report settings to explicitly convert the text reference field that uses the 'ToText()' function to convert the value to text. Then, you can map this formula field to the key field instead of the direct mapping from the text reference field. Make sure to back up your data or work with a test environment to avoid any unintended consequences.
Sorry I was not of better help. Please let me know the solution that customer service comes back with so we can help others who may encounter this.
------------------------------
Justin White
------------------------------I tried using another pipeline to do the same thing off of a different table, where I would use just another text field instead of a related field. It leads to the same error. As for your suggestion on using "[Related Member]", how would that go into a pipeline query? I didn't think referencing a field could be done outside of jinja syntaxes with the { }'s.
------------------------------
James Carr
------------------------------Apologies for any confusion caused. No, Quickbase does not use square brackets [] to reference fields. I apologize for the incorrect information in my previous response. I was trying to think of a way to fix the template syntax, but I edited that info out of that response.
Again, sorry I was not of better help and please let me know the solution that customer service comes back with.
------------------------------
Justin White
------------------------------