Table record metadata access from function?

When loading a table record inside the “get table record” action in a function, it seems that metadata is unavailable. Is this by design? Is it possible for me to allow a function to read metadata from a table or do I need to pass it to the function first?

I have seen that in the past this data was hidden from table record widgets, but that was fixed. Is a similar fix required for functions?

Hey @enewton, functions mirror automations here, and triggers can’t read record metadata either. Curious what you’re using it for though. Is it created/updated time for something like a date comparison, or something else? That’ll help us figure out where it fits.

Yes, @atrabuco, that’s right. I’m using a connector function to fetch records from a SQL database in a loop, and comparing the creation date of each record against the record being created on the Tulip side. Our app uses a looper widget with a connector function, and this logic will probably be replicated in other apps we use, so I am putting the whole thing in a function.

For now, I can just retrieve the datetime in trigger logic and pass that to the function. It’s not too bad in this case. But, I am just getting started and I imagine there will be other cases where it’s not so convenient to do so.

Got it, thanks for following up so quick. Passing the datetime in from the trigger is the right way to do it for now. If you hit spots where that gets awkward, one pattern is to add your own timestamp column that gets set when the record is created. Functions can read that like any other field. Please keep posting those cases here as you find them, since they’re what we’d use to decide whether metadata should come to functions (and to automations along with it).