Skip to main content
Solved

Trouble with error handling on Card Move through API

  • February 17, 2022
  • 1 reply
  • 377 views

daniel-levy2

Hello everyone,

I am developing a simple application that will be integrated with Pipefy, and I will need to allow cards to be moved between phases with calls to the GraphQL API. The issue I am having is that there are certain fields that need to be updated before a card can move to a particular phase. When those fields are not set and the API call is made, the error that returns is very general: “Card could not be moved to phase id: <ID>”

Is there anyway to make this error message more specific so that I could display to the user why it is failing? I thought I was able to do it when experimenting through Postman but now I cannot seem to find the call I made

Any help on this would be greatly appreciated

Thanks!

Best answer by genietim

As the error is always due to fields that were not filled in, you can simply query the fields on the current phase of the card and check whether they are required or not, and whether they are filled or not. That way, you can determine the erronous fields yourself.

View original
Did this topic help you find an answer to your question?

1 reply

genietim
Forum|alt.badge.img+12
  • Pipefy Legend
  • 412 replies
  • Answer
  • February 18, 2022

As the error is always due to fields that were not filled in, you can simply query the fields on the current phase of the card and check whether they are required or not, and whether they are filled or not. That way, you can determine the erronous fields yourself.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings