Marketing Cloud Package Manager

Hello,

I am using the placeholder in an Automation's SQL Query, prompts it when deploying the JSON Package but it does not populate with the value I fill it with, and maintains the placeholder string.

Maybe this is not supported? eventhought the documentation says it does.

Thank you for your help

We have discovered a hidden requirement for publishing Installed Packages, which is that a Business Rule must be enabled by someone at Salesforce for the BU wanting to publish the package, and that is after the components have gone through a security review. Furthermore, that Business Rule will only be enabled long enough to publish the Installed Package, and will then be disabled. This is the same process any ISV goes through today when wanting to create and publish a new app via Installed Packages, but the security review and temporary enabling/disabling of the BR was news to our team.

We are working with our platform and framework teams to streamline this process. In the meantime, you will need to log a case with support to get escalated to the team that can approve the request for your BU.

Apologies for the extra steps that weren't documented. Once we finalize a process, we will ensure docs are updated accordingly. Thanks for your understanding, and we look forward to hearing your input on this and other features for the roadmap!

When you use package manager to move a collection of cloud pages, be aware that it will only move 49 and the rest of the cloud pages will not be picked up.  You are unable to select individual pages so if your collection has more than 49, you are out of luck.  We had to copy each landing page into different collections of less than 49 in order to use package manager.  We also hit a limit when moving assets in content builder.  Cloud pages acts like it packaged all your pages, but doesn't.  When selecting assets for more than 50, it simply crashes.  You have to manually select 50 individual assets at a time, package and repeat.  SF is aware and are working on the bugs.

Hi Guys,

Is there a roadmap for package manager on new features ? One of the pain points we noticed is that if we create a package say with an automation and package manager complaints of dependencies, we cannot easily remove the one with issues and move on. We have to go all the way back and remove all the items and re ada the new ones. So let us know on the roadmap and is this worth mentioning to clients to use for deployment?

Buyan

An early adopter discovered an issue where the zip file generated by MC Package Manager was not compatible with Windows 10 and thus would throw an error when attempting to deploy the package. This was resolved on April 27, 2021, so Windows users are unblocked from using the deploy feature.

MC Package Manager Help Docs