On the main card, I added 'CBT' value 018 first. Then I clicked the button called Process Work Checklist:
add item "{{%CBT}} Draft Process" to checklist "Process Work", add item "{{%CBT}} Community Testing Process" to checklist "Process Work", add item "{{%CBT}} Final Draft Process" to checklist "Process Work", add item "{{%CBT}} Backup Data Process" to checklist "Process Work", convert all the items in checklist "Process Work" into linked cards using pattern "{cardlink}", for each card linked from an item in checklist "Process Work", set custom field "Card Type" to "PRW"
This created a checklist like this (with a Hyperlink that connects a new card):
018 Draft Process
018 Community Testing Process
018 Final Draft Process
018 Backup Data Process
Each card didn't include CBT "018" by this automation rule:
when custom field "CBT" is set in a card in list "Trigger", for each card linked from an item in checklist "Process Work", set custom field "CBT" to "{customfieldvalue}"
Am I missing anything?
Hi @Philippe Gallant ! So just to summarize, you've created a rule that says:
when custom field "CBT" is set in a card in list "Trigger", for each card linked from an item in checklist "Process Work", set custom field "CBT" to "{customfieldvalue}"
Expected result: All linked cards receive the same CBT custom field value as the trigger or parent card (in your example, all linked cards CBT custom fields should be set to 018).
Actual result: The CBT custom field value is not populated at all in the linked cards.
Are you able to clarify if you are setting the CBT field before or after the linked cards are created? The trigger is "when CBT field is set". If you follow the cadence of setting the CBT field in your trigger card AFTER the linked cards are created, then it should work. As mentioned in your last post, I'm under the understanding that in order to copy a custom field value automatically, the custom field change needs to occur in your trigger.
I can see the problem since I set the CBT field before creating linked Process Work cards. When creating a list in the backlog column, I add the CBT field value. When ready to do the work, I move the parent card to the In Process column and then use the button link (see above the button command). You noticed that I am using {{%CBT}} to create the checklist. It worked nicely. I did use {{%CBT}} to add the linked cards, and it didn't work when I tried to use the trigger, and not working. Is there a way to copy the Parent custom field CBT and paste it on each linked card?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmm yeah, I can see why that's confusing. You'd think you could create a command that:
1. Creates checklist items
2. Turns these checklist items into linked cards and prefixes the linked cards with a custom field value from the parent card
3. Finds each linked card and sets the custom field to the parent card's
It's sort of strange how action no.2 works, but not no.3. Maybe I'm missing something 🤔
Another approach could be to use wildcards. So, if all your linked cards are pre-fixed with the CBT custom field value, you could take this value and populate a custom field. In this case, I'd suggest pre-fixing these linked cards with "cbt:"
So you'd need to create another rule that says something like:
"when a card with a name starting with "cbt: {* }" is added to the board, set custom field "CBT" to "{wildcard1}"
So, if your card button is generating a linked card called "cbt: 123 Draft Process", the custom field "CBT" would be set to "123".
Maybe there's a more sophisticated way to approach this though? @milynnus is a butler pro and might be able to help? TLDR: basically Phillipe is wanting to do the following:
1. Create card and set CBT custom field
2. Click card button and generate checklist items
3. Turn checklist items into linked cards pre-fixed with CBT number (so far so good)
4. Set CBT value in linked cards to the same value as the trigger/parent card (this part doesn't work).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Philippe Gallant @Hannah Humbert - Simpla Workflows
It is for s/no 4 that I created this endpoint
since "found", "trigger", etc cannot be appended to custom fields to allow you to update.
You can try adding another trigger to inspect the card name for the prefix then update the custom field. I think that would work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hannah Humbert - Simpla Workflows and @milynnus Thank you for your help. I used Hannah's suggesting "when a card with a name starting with "cbt: {* }" is added to the board, set custom field "CBT" to "{wildcard1}". it worked. I will explore for a better solution how to sort the list better. Much appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Hannah Humbert - Simpla Workflows I came back and tried on the previous post and expired, so I am creating this again. Hope you can help me with this. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.