Count number of submissions in week

(Pomster09) #21

Now when I tick "use default" then the keyword disappears, then how will it know what I want? 

(Nic Hubbard) #22

Now when I tick "use default" then the keyword disappears, then how will it know what I want? 

 

It was just a test to see if that worked. There are other triggers that I have found that had issues like this and I had to tick a box like that.

(Pomster09) #23

Ok, so I've cracked the simple part (thanks guys for your help so far). It took hours to figure something out that should have been the first thing to look at. Simply set the metadata value to the POST data value of the form field, too simple. Now the hard one, I need to grab the submission ID and place that in a metadata field, but the submission ID doesn't have a POST value, any ideas guys?

 

form-post-test.png

(Nic Hubbard) #24

Have you tried just putting %asset_assetid% in the metadata field any not using the trigger for that part?

(Pomster09) #25

I tried that but all that was returned was the ID of the form itself. I'm thinking I'll create a hidden form field with the value set as the keyword replacement submission ID, and then grab this in the same way. I did come across an issue though, the normal squiz date field is compiled of more than one field and this fails to post every time, and it also makes the other triggers below this fail too. On the front end of the form I use a jquery datepicker to populate a single field, then split the field up before posting to squiz. I'll just delete the real date field from the custom form and replace it with a text field. This should work...