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.
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 Row ID to just Row_ID ? or will it break anything, I’m not sure if that’s a system thing.
@Jazz,
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.