Issue Summary

When Butler creates multiple cards in sequence, the card related variables used in creation always reference the most recently created card, not the original card the button was pressed on.

However, there is the concept of 'trigger card' which allows reference to the card the card button was pressed on, which should be used in this case. Unfortunately there is a defect causing custom fields to not be available as trigger card variables.

Steps to Reproduce

1. Create a custom field named TEST
2. Create a rule referencing that custom field

   when custom field "TEST" is set by anyone, create a card to the bottom of list List 1 named "{{%TEST}}, create a card at the bottom of List 2 named {{%TEST}}" 
    
   

Expected Results

Both of the cards should reference the trigger card, allowing the card name to be changed.

Actual Results

Only the first card will carry the custom field value with it.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available