the personal blog of adam spriggs
Sometimes it’s handy having a list of Content Builder Assets by folder in a Data Extension, especially for migrating Package Manager.
Before you add this Script Activity in Automation Studio, add your API creds and update the Category ID for your target Data Extension. You can also update the query criteria starting on line 91, if needed.
As always, let me know if you have any feedback in the comments below (or on Github).
Instrumental version here.
I got away with… everything, under the last boss, and it wasn’t good for me, at all. So, I want guidance. I want leadership. But don’t just, like, boss me around, you know? Like, lead me. Lead me… when I’m in the mood… to be led.
~Ryan Howard, The Office (US), Season 7, Episode 25, “Search Committee”
I don’t know about you, but I’ve found monitoring crucial File Import Activities in SFMC a challenge. I think it’s important to ensure all of the rows in the file got imported or have some recourse to identify exceptions — outside of accessing the results file that gets dropped in the SFTP Import folder or relying on the import results email.
Here’s a script that retrieves and iterates through the ImportResultsSummary SOAP object data (via WSProxy) and writes it to a Data Extension of the same name.
NOTE: The
DestinationIDis either aListIDor theObjectIDof a Data Extension. If you’ve got an inventory ofDataExtensionSOAP object data, you can use something like this dataset to build a pretty comprehensive report on import exceptions.
I started setting proper Customer/External Keys on all Import Activities after using this data, just so ImportDefinitionCustomerKey is meaningful. One less thing to have to track down when troubleshooting.
Of course, I welcome any feedback y’all might have on this.