Gary_Verster2

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 text field, I lose 4 hours! Strange.I guess the alternative is for me to add a timezone to the Change Log, i.e. EST (or wha...

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-break-token/) instead of using a pipe; just wanted to get the actual timestamp bit populating correctly first. Marketo se...

Hey Jason, have you managed to work this one out yet, chap? Would be useful to know... for the same reason - clean up!

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 process just yet... explaining that they need to enable macro's and then showing them how to run the fix is probably a ste...

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 in the solution). The chances of getting a comma in an address field is not exactly low, so what should be a relatively ...

This is crazy. Any word from marketo on the Support Case?

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 enabled and then importing with 'auto-detect' enabled. Seems to keep the special characters and map the fields... we're going...

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 delimited option, and then suddenly this week we started havng the same problems that Danny is having. We haven't made ...