Jump to content

What is stopping data in ICF fields appearing in the Request when using "h_custom_x" as form Field ID?


Recommended Posts

Posted

I feel dumb asking this after my experience but a new form is not passing through the data as expected.

Data entered into a custom form with this config:

image.thumb.png.91ff49291d0da2e970d0b64a0a37344c.png

Shows in the questions on the Request that is logged:

image.png.8c0f8e2500313fdae0bc8027377b3533.png

But does not appear in the Request (and therefore does not show in the Request Details custom form fields) - and verified by running autotask to send me the contents of these fields:

image.png.c8408246d8c07c4689a84aa79b5a0150.png

So what is stopping h_custom_p getting into the Request?

The h_summary and h_description from the first custom form are getting through ok.

  • Berto2002 changed the title to What is stopping data in ICF fields appearing in the Request when using "h_custom_x" as form Field ID?
Posted

My initial thought was that the data was not suitable for the type of Custom Field (I fell foul of that one, so its ingrained now 😄) but you have used P which is unlimited text.  Theres no hidden space at the end because they're not accepted, so I think this looks OK.  Is the Workflow overwriting / blanking it? What happens if you choose a different CF? Remove the node and start again?

Posted

I opened the form today and the custom value field IDs were not there; which explains why they did not work.

I can only conclude that the form had not saved and published.

image.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...