Forum Discussion
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
------------------------------
- JamesCarr12 months agoQrew Trainee
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
------------------------------- JustinWhite12 months agoQrew Member
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
------------------------------- JamesCarr12 months agoQrew Trainee
Acknowledged. I will definitely share a solution if and when I get one.
------------------------------
James Carr
------------------------------