Supporting Gallery Data Connections in Macros run on Private Gallery

[Laszlo_D]

This is an issue that has been marked as solved, however it isn't.

The problem still persist. When you have a macro with a gallery data connection, the workflow containing the macro gives an error when run on the server: 'Unable to translate alias'

If you select manage assets, then include any macros when you publish, this bug is gone. That's the fix. 
But this is not a solution because if someone updates the macro, the containing workflows will still use the old, included version of the macro. You will somehow need to remember which workflows use the modified macro, download them all, include the new version of the macro and republish the workflow. 
Well, I can't see how this is a fix to the problem. It's probably better to just keep using the old disabled container 'fix', which is also quite painful.