When I automate a typeform card to move from a list to another board, I lose the answers.

[CHRISTINA HATHAWAY]

Hello!  I am trying to create one board where my client weekly check-ins live.  I have created individual typeforms that have their own individual boards.  I have used the "power up" option to connect typeform and Trello on each board.  When a typeform is completed,  it comes over the the correct board with all of the answers intact.  Then when I move or copy the card to another board,  the answers disappear and all I have is a broken attachment link.  This is also true using the automation Butler.  

Can anyone help with this?

[milynnus]

@CHRISTINA HATHAWAY 

I have worked with Typeform a bit to extract the data and make them available to be updated on the card. I am not surprised, in your case, since the data lives inside the power up, probably as an attachment section. Would be any different if the power up is activated on the destination board? 

[John Chambers]

@CHRISTINA HATHAWAY @milynnus 

I was having the same issue - we have a TypeForm that customers submit requests with and while it comes into the Request Form Board a'okay - when we would click the button to move it top a different board (we have Q1, Q2 etc) it would attach a link that unless you're an admin for TypeForm, one is unable to view. 

I added the TypeForm PowerUp to the Q1 Board and moved a card to the Request Board to the Q1 and voila - all the TypeForm content is there. 

SIDE NOTE - I did NOT have an attachment - so if your form has a field for someone to attach an image or a file of some sort, I can't confirm or deny that will carry over. 

Hope this helps and good suggestions @milynnus 

[milynnus]

@John Chambers 

By “attachment section” I meant the use of attachment as placeholder to expose the contents of a power up. I believe that’s what Typeform use in implementing their power up. 

[John Chambers]

You're correct - they do use that - but if you set up typeform with trello integration you should see something like this. This is a section of a request form we have. I'm sure you're already aware of this, just wanted to include an example for others.