Monday integration error with Numerics fields

Dear All,

I know that some API modification was done by Monday.com and today was the last limit and I have since today an error that appears when I create a subitem with the module from Monday : " Create a Subitem":

image

Since today, all my Numeric fields disappears, I thought I’d made a mistake and recreated them all, but getting the same error:

I also underlined that the “Value” fields is now identified as “undefined” :

image

Is it meaning, that I need to discontinue using this module and use the Graph SQL one?

Kr,

Welcome to the Make community!

For complex technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.

You can open a new ticket, or if you are unable to login for some reason, you also can reach support using the contact form on the website.

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

2 Likes

Hi @IT_Team,

Try it now and see if it works, monday.com’s integrations platform was down yesterday about the time you posted your issue.

You can see the incident here.

Hope this helps

2 Likes

Dear all,

Here a quick resume of the issue encountered and how I fix this one.

Before yesterday (14 Feb 2024 - 16h30) all my workflows were working as expected, and the issue arrive after this timestamp.

On my workflow I generate a json file from an xls document. Into the json file, the numerics values are formatted as string and I use the “,” as comma.

image

Meaning that before yesterday, the string with “,” was correctly converted into numeric by the “Create a Subitem” module.

The option I choose instead using the “Execute a GraphQL Query” is using the “replace” and “parseNumber” function into the “Create a Subitem” module :

image

Not sure if I continue to use this instead GraphQL (seams to be quicker with the Create a subitem module), but for now it works again.

Kr,

1 Like