Multiple text set column value not working

I am trying to test Multiple texts column using a Scheduled workflow for a Column called New Roles

After I run (in the Builder) the Workflow New Roles is not updated:

I create a Scheduled Workflow per the example:

After I ‘run’ it in the builder.

The column “New Role” is not updated and these is the details

Loop results:

Make Array results:

Set Column Value results:

Not sure what I am missing.

Thanks for any pointers

In addition to not testing this for Roles, I also haven’t used the new workflows. I don’t think I have a team that has access to the new workflows. So apologies in advance if I am steering you down the completely wrong path.

Out of curiosity, what happens if you let the scheduled workflow trigger run at it’s scheduled time. Just wondering if it still kind of runs client side when you click the run button.

After reading your previous feedback I set the scheduled workflow to 5 minutes since it might be client-side v server-side issue so I will update shortly :slight_smile: . Very shortly!

1 Like

Didn’t work - still does not update. All the data looks the same as above; set as a Scheduled Workflow for every 5 minutes. New Roles is a Multiple text column and the Make Array creates an array as shown. The Set Column looks like it works per the run log…but….no update to the Google sheet. I am also going to try a scheduled workflow on a Glide table

Wait…did you set that column as user specific? Server side processes have no concept of a specific user, so they can’t touch user specific columns. The server wouldn’t know which user to emulate.

Not user specific columns.

But this methodology did work properly against a glide table. I updated the test: first table is a Google table; the second is a Glide table. Snapshots (below) from the Data builder show the google table did not update but the Glide table did. I manually synced the Google tables just to be sure. Unclear if this is a feature or a bug.

Data results for the Google table:

image

Date results for the Glide table:

image

It defaults to user specific when adding it to a google sheet table because it’s a column type that can’t be written to the actual google sheet, so it has to be stored internally as a user specific column (dumb, I know). It’s been a while since I’ve seen this but it’s not a new thing. You can tell by the column header icon color that it’s user specific, but you also can’t uncheck it when creating the column. So yes, it would only work with a glide table.

I would note that when updating the Google table Glide uses the “google column name - New Roles”. Maybe this is the source of the error because when updating the Glide table Glide uses the “internal Glide column name - ‘Sme0s’ (instead of ‘New MT’)”

Google Table

Glide Table

Nope, definitely because it’s set up as user specific in the google sheet table. Check it. The user specific checkbox will be checked. I think this was apparent to a lot of people when the Multiple Images column was first released as it also defaults to user specific for google sheets because you can’t store arrays in a google sheet cell, so it has to store internally within glide instead and that internal storage forces it to be user specific and thus the workflow can’t write anything to it. I’ve never understood why it had to be user specific, but I think it was just a coding shortcut on Glide’s behalf to use existing code functionality. Never made sense, but they also never bothered to correct it.

This is from the Data Builder which is why I did not think it was a USC.

BUT……to test your theory I created a new Multiple texts column AND the User specific column was checked and I could not uncheck it.

Glide should show that in the column details

Thanks for the insights Jeff

Agreed, but that teal icon color tells you right there that it’s user specific.

1 Like

And that is also something new I learned today :smiley:

1 Like

Hehe, that’s why I’m such a big proponent of asking for screenshots. There is a lot more information there than people realize. At the very least I can say that I was somewhat useful today. :grin:

2 Likes