We are using SDL Tridion Sites 9.1 and currently we have custom tool(Internal) for Publishing /Unpublishing items in multiple publications at once.

Recently one of the publisher asked us to look into below option.

enter image description here

Is it okay to create a Fake publication, so that users can simply use that publication to publish and unpublish to all child publications.

what are the disadvantages of this implementation?


2 Answers 2


I've seen this done in a few implementations. The main things that spring to mind to watch for are:

  1. Licensing implications, if you're paying per Publication then there may be a threshold that one extra takes you over (then it's ALL YOUR FAULT ;) )

  2. Naming. Don't give it some funky technical name, discuss it with the editors that will be using the system and ensure it makes sense to them

  3. Over-publishing. Editors are busy people. They don't like doing things twice (probably the reason you've asked this question!) but that may also mean they're happy to do something once ... even if there's (technical) waste. Be sure the design means only what needs to be getting published is - and if not - then the editor is aware of the implications and takes responsibility for that.

  4. Do you have workflow? Check if publishing things to the 'other' targets in the workflow state they will be in is going to work as expected.

Of course, I'm assuming you're looking at only a publication or two so it won't have much impact in terms of topology complexity... but something you will want to consider too.


There is one additional tech debt to this:

  • if you allow publishing from this publication then you have all these records in the broker database, which brings up the size of the broker. You can mitigate this with a custom resolver where you remove items during the resolving phase so that these transactions are empty, so you are complicating architecture to fix the size of the broker.

As you see, it gets complicated really easily.

What I would suggest to you is analyze your blueprint. See if you can already reuse some publications for this. In general, the sample blueprint structure provided on docs.rws.com is really great example how it should be setup. So don't reinvent the wheel. Just use it.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.