Okay, fun feature of Workflow Studio (DC version), adding a generic template value in the "Create Record" action will clear out the table. Setting the table clears out the template value. I'm sure their devs didn't mean to make a "click here to win" game with the moving button, but that's kind of what it feels like.
The only way I have gotten it to work is to hand in a template input variable that is set to "Template Value.{table_name}".
Anyone else seeing this? Found any way to use the Look Up Record value to set the Template Value?
(We are on glide-washingtondc-12-20-2023__patch4-hotfix1a-07-01-2024.)
Here's an example. I created two inputs:
- "Contract template" which is of "Template Value.Contract" type, and
- "Generic template" which is of "Template Value" type.
I also have (what I would prefer to use) a "Look Up Record" action that queries for and returns a template record. This is preferable so that the slower, more data intensive actions like queries can be kept in a sub-flow and out of the main flow.
 
Now, let's start with a "Create Record" action with the table set to "Contract" [ast_contract].
If I drop in the generic template input
 
This is the result
Same occurs with the look up record template value. Both are accepted but they reset the table value. If the table is set,
 
 
We're back to where we started.
 
 
If we drop in the "Template value.Contract" input though, I think it still resets the table but then sets it to the Contract table as part of the transaction.
Voila
 
The reason I'm thinking this is because if you start with a blank table and template value
 
then drop in the "Template Value.Contract" input,
It also works.
 
It gets better! If I try to test my new subflow, instead of giving me a reference choice pointed at the template table, it displays the same non-functional "Drop in a template..." interface?!? Along with the 'Select a field' and 'Add field value' controls like it's on the Create Record action. Deeply weird.
