Skip to main content

new fields added to "Financial Document" model not working

I've created a new "Financial Document" model (in V2) and added a custom field called "Expense Type", but it's not working as expected. However, when I remove all the existing nodes in the model, it functions correctly. Can you help me understand why this is happening?

I also tried adding another custom field, "Expense Date," with the same prompt text as the last item, but it didn't work. When I moved this custom date field to the top (as the first item), it worked fine.

Status: Completed8 comments

Log in to comment and vote

Comments8

  • Cplus IT

    •

    Jul 22, 2025

    Hi Mohamed,

    I've checked on my end, and the issue still exists. I tested it by creating a new model (ID: *****8f46-9de222a80c08).

    • Mohamed Biaz

      •

      Jul 22, 2025

      Hi @Cplus IT
      I've tested the model ID you provided on my end but couldn't replicate the issue.

      Could you please share:

      • The specific field where the problem occurs

      • The exact steps you followed when encountering the bug

      • An anonymized document if possible


      This will help me reproduce and investigate the issue more effectively.

  • Cplus IT

    •

    Jul 22, 2025

    Hi Mohamed,


    Could you please extend the trail period. I have sent an email last week for the same.

    • Ianaré Sévi

      Team•

      Jul 22, 2025

      Hi,

      We’ve updated your trial period until August 6th.

      Thank you for your help in improving our product!

  • Mohamed Biaz

    •

    Jul 16, 2025

    Hi @Cplus IT The release is now live. I've just tested it and everything appears to be working smoothly in production. You should be all set on your end as well.

  • Cplus IT

    •

    Jul 16, 2025

    Hi Mohamed, any updates on the deployment?

  • Mohamed Biaz

    •

    Jul 11, 2025

    Great news! The issue has been resolved and will be deployed very soon. We'll keep you informed of the update. Thank you for bringing this to our attention.

  • Jonathan Grandperrin

    Team•

    Jul 8, 2025

    Hi! Thanks for this report, we were able to reproduce the bug. We’ll let you know once it’s fixed.