Float to string

pedro.syngenta.udi

I'm doing an automation through Power Automate, but it only recognizes string values and Smartsheet columns are in float, how can I do this integration?

error that appears API 'smartsheet' returned an invalid response for workflow operation 'receive' of type 'OpenApiConnection'. Error Details: 'API operation 'GetSheetData' requires property 'body/value/43/Official Lot' to be of type 'String', but it is of type 'Float'.'

Genevieve P.

Hi @pedro.syngenta.udi

I checked in the Power Automate Community and found a similar thread that may have a solution you can use: API Operation expecting data of type number but if of type string

In this scenario, the user either removed then re-added a connection and/or removed/re-added any steps using the connector in a flow and retested because their existing connections and actions were still referring to the old OpenAPI definition.

If this hasn't helped, I would recommend posting in the Power Automate Community to get help from other Power Automate users.

Cheers,

Genevieve

Bruno Cerentini

I am having the same issue.

SergeantPup

For others with this issue, this is how I solved it. For me, the error was for the "Row ID" column which I have to have for every smartsheet because they don't pass the Row ID through the dynamic content function so you can actually update rows (but I digress). It was giving me specific row number errors and I recopied the row ID's one by one into the field and the errors resolved one by one. But when I replaced them all, it still said the Row ID in row 0 was not formatted correctly. Well I have no way to fix row zero. I also deleted any excess 'blank' rows at the bottom as I know this can sometimes cause issues. Finally, I copied the contents of the column into another blank sheet, deleted the Row ID column, saved, then re-added the Row ID column and recopied the values back in and it immediately started working. I have no explanation, I just know how I overcame it and I hope it helps others that come searching for it.

AdamsR

@SergeantPup I tried this solution several times, but every time I test my workflow after fixing it, it will work once and then have the same error again. Do you have to continuously do this as a work around?

SergeantPup

@AdamsR

I genuinely didn't know which sheet this was because I didn't reference it in my post but I recalled it being approximately 16 rows long so I went looking. And wouldn't you know it, when I look on the date of my post, I see where I had several failures and then I had several successful runs on 4/7/2025. For 5/2/2025 (the next time it was expected to run) it failed. When I investigated the error, it sounds very similar to what I reported on 4/7/2025:

So to your point, no I don't think a sustainable solution has been found because the very next time this ran (a month later) it barfed again for that Row 0 error. The really weird thing is this is a very basic function. The function it's barfing on is just the get sheet data function (which I use in literally every automation involving smartsheet)

Perhaps @Genevieve P. has more recent insight into this issue since 2022.

The immediate workaround would be to send a raw HTTP call to get the sheet data. I'll have to look up how to fashion that call and bypass the native get sheet data function.

SergeantPup

@AdamsR

I messed with this some more today. I followed my steps from last time and I kept getting the same error. I removed the column and re-added it multiple times and I had the same issue.

When I ran my Row ID labeler script again (to replace all the values without me copy/pasting) it started working again. I don't have a firm explanation for this but I've got a theory. When this happened last month, I manually copy/pasted the row IDs from right clicking the row and pasted them in my row ID column. I noticed when I spit the column into Excel to store it while I deleted/readded the column, some of the numbers changed on the very end of the row id. I made sure excel was formatting it correctly and ultimately just ignored the problem and copied the column into smartsheet instead because I assumed this was some sort of smartsheet to excel translation error.

Running theory is when I did the manual copy/paste of row id's from right clicking and pasting into my column, something got messed up and then me doing it again today was still throwing the errors. That doesn't explain how it worked after my testing last month but I can confirm it worked in testing again today after I let Power Automate label all the Row IDs. It also doesn't explain why the error persistently references row 0 which I have no way to alter and I don't know how/what it means by the value in Row 0 is supposed to be a string but got a float (there's no such thing as row 0 unless it's a backend thing I'm unaware of).

The real test will be if I'm able to get it to work tomorrow. I will run the automation again tomorrow and see if I get any errors. For now, the problem seems to be resolved by me running the Power Automate script to label all my rows vs how I manually copy/pasted this information last month (because it was only 16 rows).

SergeantPup

Looks like it worked today 🤷‍♂️