An Uncaught (in promise) error

Answered

7 Comments

  • Skip Moore

    try something like this

     

    client.invoke('ticketFields:custom_field_' + metadata.settings.Custom_Field_ID + '.hide');
     
    where metadata.settings.Custom_Field_ID is a var for me 
    0
  • Noe Jimenez

    Hi Skip,

    Thanks so much for responding. It appears that the settings for my metadata do not have a Custom_Field_ID. Should there be one present? This is possibly the root of the issue?

    I tried to set the id to that particular var that you suggested, but have not had any success. The same error as above persists. Still investigating. 

     

    Thanks for reaching out regardless!

    0
  • Skip Moore

    the Custom_Field_ID specific to a app I built it was just meant to be a example. 

    if you know the ID of the field you could test it like this

     

    client.invoke('ticketFields:custom_field_123456.hide');

    just replace the 123456 with your ID 

    0
  • Noe Jimenez

    Hey Skip, 

    For sure, I thought that Custom_Field_ID was just an example, but thanks for clarifying. I tried what you suggested above, but the same error occurred unfortunately. Could this be happening because I have not updated the rest of the application to the V2 api?

    Much thanks!

     

    1
  • Noe Jimenez

    Hey Skip, 

    For sure, I thought that Custom_Field_ID was just an example, but thanks for clarifying. I tried what you suggested above, but the same error occurred unfortunately. Could this be happening because I have not updated the rest of the application to the V2 api?

    Another thought. I am testing my app locally, but could it be that I need to install this app in order to solve this error? Secure requests don't work unless an app is installed...

    Much thanks!

     

    0
  • Skip Moore

    You will need to upgrade the whole app to get this to work . 

    0
  • Noe Jimenez

    Hey Skip,

    I already have the app_scaffold from the github repo, and have updated a bit of the code already, but if the entire app needs to be using the updated API in order for this one function to work, then I shall go that route. 

    Thank you so much for your patience, and for your help!

    0

Post is closed for comments.

Powered by Zendesk