Forum Discussion

ChrisNewsome's avatar
ChrisNewsome
Qrew Captain
3 years ago

Pipeline issue: "invalid literal for Decimal" ???

What the heck does this mean? I can't seem to figure it out.
("1170 Martingale" is the name of the record being modified to trigger the pipeline)

I have no idea what the export fields are referring to either. I can't even seem to locate a discussion on here similar to this. Any ideas out there? The pipeline fails to produce the action because of this error.

Validation error: Invalid literal for Decimal: u'1170 Martingale'

Input (Options)
table:"bkcuzgpzg"
export_fields:Array[6]
0:"112"
1:"7"
2:"159"
3:"148"
4:"157"
5:"177"
Input (Mapping)
related_opportunity:"{{a.opportunity}}"
related_customer:"{{a.opportunity_contact_full_name}}"
scheduled_for:"amanda@getnewclosets.com"
schedule_status:"Scheduled"
scheduled_date_time:"{{a.updated_at}}"
related_company:"{{a.opportunity_company_name}}"
activity_type:"Schedule LE"​


------------------------------
Thanks,
Chris Newsome
------------------------------
  • My guess at some possible reasons...

    • related_customer is a numeric field being populated by a 'name' text field, the 'name' has a NULL value, or it is populating with a decimal value when it should not.
    • related_company is a numeric field being populated by a 'name' text field, the 'name' has a NULL value , or it is populating with a decimal value when it should not.

    If the field types match and the issue is with a NULL value, you will need to add a check to determine if it is empty first before trying to populate it.

    This is an example of what would go into the "Related Customer" field in the Pipeline:

    {% if a.opportunity_contact_full_name is none %}
    {% else %}
    {{a.opportunity_contact_full_name}}
    {% end if %}

    or shorthand

    {{ a.opportunity_contact_full_name if a.opportunity_contact_full_name is not none }}

    If the fields are both numeric and not null, I would add the int filter to the end to remove any decimal.

    {{a.opportunity_contact_full_name|int}}

    If you haven't checked it out I recommend my course Intro to Jinja for Pipelines

    -Sharon

    ------------------------------
    Quick Base Junkie
    ------------------------------
    • ChrisNewsome's avatar
      ChrisNewsome
      Qrew Captain
      I'm not sure I followed all of that. Automations were so much easier than Pipelines. Why can't it just tell me "Hey, THIS ----> is the problem, fix it"? :)

      I'll see what I can figure out from your info, thanks.

      ------------------------------
      Thanks,
      Chris Newsome
      ------------------------------
    • ChrisNewsome's avatar
      ChrisNewsome
      Qrew Captain
      OK so apparently Pipelines will not allow you to drag a field that's a number into a field that's text. I still cannot figure out what's causing this issue.

      ------------------------------
      Thanks,
      Chris Newsome
      ------------------------------
      • PaulPeterson1's avatar
        PaulPeterson1
        Qrew Assistant Captain
        You could create a field that is a text equivalent of the numeric field, ToText([Numeric Field]) and pass that value into the pipeline.

        ------------------------------
        Paul Peterson
        ------------------------------