Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
For anyone that stumbles across this. Please vote (up, not down ) on the Idea I created, and make my dream come true!
I've heard whispers that there are some backend tools that allows for querying custom object data. I think it would be very beneficial to expose this functionality in the UI so that we can export custom object data for various reasons. Top of mind, this can be useful to store the GUIDs externally, o...
With the power of search, it doesn't seem like this is possible (maybe it'll be tagged with a soonTM), unless something has changed.
When I glanced at the documentation over at developers.marketo.com, I saw that it is possible to query records if one of the searchable field values is known. Maybe I am blind and missed it in the documentation, but has anyone come across a way to export all custom object records from a custom objec...
I am fairly sure it is caused by campaign flow actions that communicates to Salesforce (such as Sync to SFDC). Maybe someone from Marketo can confirm. Or I suppose you can easily test it by running a single flow action a couple of times and see if it logs something in the SFDC login history.
I found that you actually don't need to have an active session. You can come back to it later by right clicking on the list an selecting Export Status (or something similar). But full export is probably best handled via the API IMO.
Kenneth Elkington, wondering if there are any plans to explore this functionality a little more? Seems silly that one bad integration or an uncaught error/bad process can cripple the system (which must have happened before to multiple organizations, unfortunately).
Hi Ko-Chih! I didn't attempt to go any further, but I would imagine that it would eventually start processing after some time. Per the document, it says: This will respond with a status of “Queued” after which it will be set to “Processing” when there is an available export slot.Perhaps someone from...
Figured it out, /rest/ isn't supposed to be there.
I noticed that too as I was looking through the endpoint page, but yields the same result: