I tried using the {{system.dateTime}} token, too. Same result...As you can see here, the Timestamp field is populated just fine, but as soon as you 'write' the timestamp to the tex...
Hi Mark,Thanks for the reply, chap.Yeah, I was planning to prepend to the Change Log using Sanford Whiteman's line-break token trick (http://blog.teknkl.com/dark-mkto-alleys-line-b...
Hi everyone,In preparation for GDPR next year, I'm trying to create a text field that will capture every change that our users make on our preference centre, including a timestamp....
Thanks, Sandford. As per Dan's reply, thanks for working on this and coming up with an interim solution.That said, I won't be retraining my marketers on how to upload using this pr...
Hi Said,Yeah, the comma-separated UTF-8 upload is always a fallback, but this could introduce extra columns into the data (which is why there is the 'Open in Wordpad/Notepad' step ...
We've been doing some more testing today (in spite of Marketo telling us that they can't replicate the problem!)... and we've had some success with saving as a csv with UTF-8 enabl...
Hi everyone,We're experiencing the same issue. We've been uploading Unicode .txt files from a standard upload template for the last 18 months with no problems, always using the tab...