Casey_Grimes

Hi Jacek, So, you're really looking at two separate problems: 1. Determining the proper Case to pull content into the email is going to happen through Velocity. Now, depending on your logic on how to match Case to email content, there'll be different logic to write in Velocity (or else I'd at least ...

Agreed with Sanford--why not use the existing link ID setup? I do something in a bit of reverse where I assign all of an email's standard links (logo, social icons, whatever) a specific link ID prefix so they may be screened out for reports, Smart List triggers, and so forth. There's an appropriate ...

So, what you're describing is essentially an ETL tool's responsibility, and there are plenty that work with both Marketo and Azure SQL DWH/Azure Data Lake; both on-prem (Boomi, Alteryx, et al.) and SaaS (Fivetran, Stitch, Alooma, et al.) ETLs can handle this sort of work on a scheduled, automatic ba...

The offset you receive in the response from the endpoint lets you page through total results per the max return you've set--so you'd continue paging through the results via offset until you hit a number under 200. At that point, you'd have your count of folders. There's no meta "total" value, as the...

On a basic level, Marketo writes cookies to the domain .example.com, meaning that the cookie should be readable from any given subdomain. Now, there are complications with two-letter TLDs, and if you have a non-standard deployment of how your cookies are recorded, that can cause issues.But, by defau...

Based on the information you've given so far, it's actually pretty hard to tell why this might be happening. I would at least start by seeing if there's discrepancies by source (form integration vs. upload), because it sounds like the object setup itself is fine--it's getting the data in. Look for p...

Yes, this can be done--I personally do a variant of this using fieldsets to determine pages rather than multiple forms--but it does require some JavaScript development.

In a case like this, your best bet is probably to handle such a redirect at the DNS level. Now, while it's strongly discouraged because you're doing two lookups, it's totally possible to do something likeinfo-old IN CNAME your-instance.mktoweb.com.info IN CNAME info-oldSo when you look up info, it g...

Again, I'm a little confused--how is that different than the existing description aside from UX/placement? I'm not trying to be obstinate but just trying to understand how that differs from today's description, which can be added under the field name per my screenshot.