Cheat sheet for dynamic text variables?

I’ve noticed that the default home page includes {LOGGED_IN_USER:NAME} on the page.

Not saying it doesn’t exist, but I can’t find any documentation on these – are there more we can use? Could I grab {CURRENT_RECORD:NAME}, for example?

Anyone have a cheat sheet for these?

Hey @justinjtessier !
Thank you for your question!

By default, Softr supports the {LOGGED_IN_USER:NAME} variable, which automatically grabs the name of the logged-in user from the table connected to the Softr users connection. This pulls the user’s related data directly from the users table.
Here is a document in regards to this.
While {LOGGED_IN_USER:NAME} is the main built-in variable for displaying logged-in user data, there could be some custom codes to grab additional parameters from the user’s data or other records.

As for {CURRENT_RECORD:NAME}, it is context-dependent and refers to a specific record in a list or database block, not the logged-in user. This placeholder would be used when you’re viewing a particular record on a page (like a record detail view). If you’re trying to display user-specific data that isn’t tied to the logged-in user.
For example The list detail block automatically shows the current record when there is a record ID in the URL.

Best,

Thanks for the info.

Is there a list anywhere of all the current built-in variables that can be used without custom code? It sounds like you’re saying {CURRENT_RECORD:NAME} would be one of them – are there others?

Is the format simply {CURRENT_RECORD:[property]} and we can substitute different property names in the square brackets? Is it the same for {LOGGED_IN_USER}?

Hey @justinjtessier

Thank you for your question!

There isn’t a concept like {CURRENT_RECORD:[property]} because list detail blocks already display the current record’s data automatically when a record ID is in the URL. You don’t need to use placeholders for this—it’s handled by the block itself.

As for {LOGGED_IN_USER:[property]}, we currently only support displaying the logged-in user’s name via {LOGGED_IN_USER:NAME}.

If you have specific requirements beyond this, feel free to share.

It would be really useful if custom code blocks where html can be entered in a “free form” style, I could sprinkle {CURRENT_RECORD:[property]} variables.