Skip to main content
Best answer

Hide input field with computed property not working.

  • March 18, 2020
  • 4 replies
  • 1212 views

Hello everyone,

I’m attempting to create a field to determine whether something is built with the CLI or the web interface via an input field.

{         key: 'isWeb',         computed: true,         type: 'boolean',

        required: false,

        default: ‘yes’       },

I would like for it to be invisible however the computed property doesn’t seem to be working.

How would I create an invisible input field that is already populated?

Best answer by Danvers

I just wanted to share the response from our Support Team in case someone has a similar question:

 

This depends a bit on your specific setup, but the general idea is that you'll need to:

1. Use either OAuth2 or Session Auth
2. Define the computed field in the auth definition (sounds like you've done this already)
3. Return a value for that field from the auth method (oauth2Config.getAccessToken or sessionConfig.perform)

 

The key point being that an Auth step is needed for this work. 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Danvers
Forum|alt.badge.img+12
  • Zapier Staff
  • March 20, 2020

Hi @DL_CharlesM I think that this one is going to be a bit too tricky for us to solve in the Community so I’ve sent this post as a ticket to our Support Team. Someone will be in touch with you via email as soon as possible. 

 

Thanks!


  • Author
  • Beginner
  • March 20, 2020

As usual, thank you for the swift response @danvers I look forward to hearing from them.:smiley_cat:


steph.n
Forum|alt.badge.img+8
  • Builder
  • March 25, 2020

Hi @DL_CharlesM - I saw that you received a response from Andrew on Zapier Support. Cheers!


Danvers
Forum|alt.badge.img+12
  • Zapier Staff
  • Answer
  • March 26, 2020

I just wanted to share the response from our Support Team in case someone has a similar question:

 

This depends a bit on your specific setup, but the general idea is that you'll need to:

1. Use either OAuth2 or Session Auth
2. Define the computed field in the auth definition (sounds like you've done this already)
3. Return a value for that field from the auth method (oauth2Config.getAccessToken or sessionConfig.perform)

 

The key point being that an Auth step is needed for this work.