Hi, Mattias

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

- I actually sent you the wrong solution, and you already got it via Email. For some reason, I thought you wanted to prefilter the table using a variable in a column, as a placeholder.

It was an honest mistake, hopefully, you can forgive me?

- After a moment, I realised your actual goal was to prepopulate a field using %VAR1% placeholder.

Custom fields cannot be prepopulated at the moment using variables; they need to be manually filled by the user I'm afraid. ( at least not with any built-in functionalities)

It probably can be done with some custom work, but our developers are very busy at the moment, working on some priority tasks and fixing bugs and issues with our plugins, so they won't be having the time for custom work in the near future.

You can always reach out to someone who does custom work, such as WP Kraken, but we can't advise on their pricing.

I will double-check with them if they know of any easy workaround and will come back to this ticket when they respond, just to confirm.

Terribly sorry for the mistake.

Hey, Mattias

- First, I want to apologise, because there is a workaround solution we came up with, I didn't see it straight away.

- Now, the column, technically, has to be set to be editable, but you can block the input so that nobody can change it from the front-end if that makes sense. Here is an example with more details:

Let's say we got a table that has a column "continent" and "countries". We will set the table to be editable, and on the column setting of "continent", we set a predefined value of %VAR1%.

- you can either set the variable directly in the Placeholders tab; in this example, we set the continent to be Europe;

or you can set the variable through the shortcode;

and it will always be the value you predefined as a placeholder.

- The best we can do about removing the ability to edit that column is this workaround:

 using custom CSS, in our case, where the column name is "continent" ( you will have to use the browser inspector to find the column name) :

- and we use this custom CSS:

input#table_1_continent.form-control.input-sm.editDialogInput {
  pointer-events: none !important;
}

- This will still make the input field visible, but it can not be changed/edited.

Hopefully, that helps.