Row ID with leading special character breaks ETL integration


Does anyone have a hack or workaround to prevent the row-id from ‘starting’ with special characters e.g. row id:


This is causing a major headache for us with an ETL integration we rely on, and I only just discovered it.

Thank you

1 Like

Depending on how data is entered into the sheet…if it comes from the app, you could use the Unique ID Special Value instead, which follows GUID/UUID standards I believe. You may still need RowID for some other functionality in Glide, so in that case you could use both, but only use the Unique ID for your ETL integration.

@jazz78 I had a similar problem. See below

@mark could you also look into this as you would do with the slash character

Rowid with slash - can that be avoided

1 Like

Thanks @Jeff_Hager unfortunately on that ETL - cannot ‘choose’ which columns to load. Greatly appreciate any other ideas?

Also on this topic - can i change the title ? if not , the space and emoji ':lock:Row ID ’ are unhelpful - would appreciate ‘Row_Id’

Thank you

Thanks @Krivo - yes i vote toss special characters out of that field, unhelpful and unnecessary.

You could try duplicating your app and changing the RowID heading then adding a new row. I’m not sure how glide will react to that.

If you don’t need RowID for anything, you could just eliminate it from your sheet and use Unique ID as i mentioned above.

thanks @Jeff_Hager - i was not sure if that would break anything.

i can try removing and rebuilding - but it forms part of another sheet, so it’s really a pain to have to recalibrate the other sheet with the new ‘related’ unique id (5,000+ records) , but yes at least it’s a workaround.

can i rename :lock:Row ID to just Row_ID ? or will it break anything, I’m not sure if that’s a system thing.


We’ll make it happen by Wednesday.

1 Like

If your ETL process is selective for the sheets you are loading you could use an arrayformula to populate the data you need onto a separate sheet with all the necessary changes to names etc.
You could either drop the Row Id and use the UUID as suggested above or wrap the value of the Row Id to make it acceptable in the ETL processing.


The above will replicate columns 1,2,5,6 from sheet TimeBookingEvent with the padlock removed from the headers.