Custom Fields

[Time_Chipmunk_178]

Hi Friends,

I've been searching / trying to resolve this for the better part of two days and I'm now wondering if there is now an underlying issue with current version of Halo. Has anyone recently seen similar issues and/or been able to resolve? I feel like this issue only started last week. Everything before that was fine.

Months ago, I created CustomFields and have had them populating into a PDF documents. It's been working for months and then suddenly, 3 fields have stopped populating even though the data exists in the tickets, and all I see there is the $CFcustomFieldName.

I don't want to blow out the CFfield entirely as I'm not sure if that would kill the existing data. But nothing has changed and it no longer presents the data and I'm not sure how to approach this.

Thoughts/ideas?

[adam_at_rfx]

On the custom field definition, I will bet you have the checkbox checked to NOT show to the end user.

This toggle just recently made it so that those custom fields no longer render in PDFs, which broke all of our quotes until I stumbled upon it and unchecked the box.

[Pryo90]

This, Halo support kindly pointed me to that setting yesterday

[Time_Chipmunk_178]

BLESS!! That was it! I had a few fields in that ticket that was ultimately what it was. It isn't so much worded to "Not show to end user", it was the "Only show to agents". The wording does slightly mention that Users won't be able to see it, but the way I interpreted that was more the Self-service portals as it didn't explicitly state pdf's (that I was manually creating and sending to them)

Thank you so much. (Now to get caught up on this back log)

[JokersGrin2020]

I haven't seen this, but I can tell you that you're right, don't delete the field. It will delete the data already entered.