Forum Discussion
Token Comma Expected during custom step to convert to duration
Hello,
I got a custom query step from another post in here as I was getting an error for any duration that went over 12 hours (just 12, not 24 - error was "couldn't parse the Duration literal). Found a solution that if I insert a custom step in place of the one to change the type to duration it should get rid of this error, but when I inserted it I continue to get this Token Comma Expected error. Can anyone see where this error is?
Hi eroyle ,
I think the previous step name should be #"Replaced Value3" and not #Replaced Value3 since it has a space in the middle.
Please make this change and see if it fixes your issue.Kind regards,
Rohit
Please mark this answer as the solution if it resolves your issue.
Appreciate your kudos! 🙂
4 Replies
Hi eroyle ,
I think there is a misplaced closing bracket (marked in blue).Kind regards,
Rohit
Please mark this answer as the solution if it resolves your issue.
Appreciate your kudos! 🙂Hi Rohit!
That did change something, but now the Token Comma expected error has moved to the name of the previous step:
Hi eroyle ,
I think the previous step name should be #"Replaced Value3" and not #Replaced Value3 since it has a space in the middle.
Please make this change and see if it fixes your issue.Kind regards,
Rohit
Please mark this answer as the solution if it resolves your issue.
Appreciate your kudos! 🙂
Thank you! This fixed the errors and I just had to replace null's with a 0. 🙂
