Conditional Fields app: What you need to know BEFORE you edit, or remove ticket fields Follow

Comments

17 comments

  • Avatar
    Dwight Bussman

    I was even more worried there for a moment. The arrow in your after screenshot example covers up the "Product" field - I thought the indexing had somehow been broken and would remove subsequent fields, too.

  • Avatar
    Dr. J

    Good point!  😉 

    Nice spot — rest assured, that was fine.

    #EagleEye #JustKeepingYouOnYourToes

  • Avatar
    Ben

    Wouldn't it be ideal if when making changes with this set of impact scenarios, that a pop up modal presented these consequences and asked for confirmation?

  • Avatar
    Dr. J

    One quick update, friends — as above, please be very careful if you are an Enterprise customer, and have referenced a Brand in your Conditional fields (or a field tied to a brand), please be sure to:

    1. Scour your rules for references to that brand
    2. Remove any rules/references
    3. Regenerate your Conditional fields code
    4. Re-edit/publish your Help Center
    5. Remove the brand
  • Avatar
    Marci Abraham

    I'm embarking on this "conditional fields" journey, and stopped here to read the warnings. We do have brands, and I'm curious about Dr. J's comment. Do those steps only apply if your intent is to REMOVE a brand? Or some other case to be aware of?

  • Avatar
    Jessie - Community Manager

    Hi Marci!

    This is actually referencing the removal of custom ticket fields. If any of your custom fields are specific to one of your brands, you'll need to take Dr. J's additional steps in consideration if you want to remove them.

    I hope that clears things up!

  • Avatar
    anu

    Hi, 

    The conditional fields app is not working for me AT all. Can someone help me troubleshoot?

    Anu

  • Avatar
    Jessie - Community Manager

    Hi Anu! Welcome to the Community!

    This actually looks like something that would be better dealt with in a ticket, so I'm going to get one started for you. Our Support team will be able to help you out!

  • Avatar
    L.A. Cayabyab

    Why can't I create conditional fields based on system fields (e.g. status)?

    L.A.

  • Avatar
    Fred Thomas

    Do these precautions apply to the "re-naming" of ticket fields? IOW, renaming the ticket field(s) does not technically change the API field name. Does the Conditional Fields app reference the name or the API field name?

  • Avatar
    Jessie - Community Manager

    Hi L.A.!

    This isn't possible because system fields can't be deleted or edited or otherwise manipulated in any way. But you can definitely create a custom conditional field to do what you need!

  • Avatar
    Stephen Fusco

    Hi Fred, 

    Thanks for your question! Renaming a field (as opposed to deleting and replacing it) should not cause any trouble with the conditional fields app because the Field ID would remain the same. The app uses the field ID not the name of the ticket field to identify it. 

  • Avatar
    Fred Thomas

    Thanks for the confirmation @Stephen!!

  • Avatar
    Jon I.

    The application hast stopped working in several of our zendesk instances. For instance, we've a condition on one field, when selecting an option several fields are shown (in any other conditions, those fields are hidden). But this isn't working anymore, as those fields are shown always. Somebody knows what's going on?

     

    Thank you!

  • Avatar
    Jon I.

    The issue is now resolved. Thanks.

  • Avatar
    Himanshu Desai

    How long does it take for a custom field to become available as a conditional field option after it is created and added to a ticket form? I'm finding that the new field is not available as a conditional option for days after it has been created.

  • Avatar
    Dan Kondzela

    We’re currently working through a service disruption. We do appreciate your report - it will help us better understand the scope and impact of the incident. Our Operations team is actively working to resolve this incident and we’re posting regular updates on our System Status Page and to our @ZendeskOps twitter feed.

    Our apologies for the inconvenience. Please continue to keep an eye on that status page for when this issue ought to be resolved!

Please sign in to leave a comment.

Powered by Zendesk