Is it possible to use ISHRemote to apply a baseline that is used by one publication to a second publication?

Hi. After looking at the various baseline-related cmdlets offered by ISHRemote I'm afraid I'm none the wiser as to if it's possible. If it is, if someone could summarise the steps to take (and cmdlets to use) that would be really useful.

Thanks!

Mike Wilkin

Parents
  • Hi Mike,

    As you browsed the cmdlets, you probably noticed that ISHRemote has not complete coverage of the public API of Tridion Docs. It gets richer every version based on the called out needs and contributions. And although many of the user interfaces try to hide the baseline concept (making it an implicit part of publication version) for simplicity. It doesn't mean that a lot of heavy lifting happens for baselines behind the scenes. Let's say that the baseline API is very rich :-)

    Now regarding your use case, just to make sure, you want to "Share a baseline" between two publications? So every time, somebody updated a version, it is valid for both publications (linked over the shared baseline). And in turn, the releasing/freezing of the baseline will calculate and require the super-set of versions selected.

    If so, then I think you need to copy the 'element' value of FISHBASELINE field of your source-publication-version into your target-publication-version, probably over cmdlet Set-ISHPublicationOutput.

    -Dave

Reply
  • Hi Mike,

    As you browsed the cmdlets, you probably noticed that ISHRemote has not complete coverage of the public API of Tridion Docs. It gets richer every version based on the called out needs and contributions. And although many of the user interfaces try to hide the baseline concept (making it an implicit part of publication version) for simplicity. It doesn't mean that a lot of heavy lifting happens for baselines behind the scenes. Let's say that the baseline API is very rich :-)

    Now regarding your use case, just to make sure, you want to "Share a baseline" between two publications? So every time, somebody updated a version, it is valid for both publications (linked over the shared baseline). And in turn, the releasing/freezing of the baseline will calculate and require the super-set of versions selected.

    If so, then I think you need to copy the 'element' value of FISHBASELINE field of your source-publication-version into your target-publication-version, probably over cmdlet Set-ISHPublicationOutput.

    -Dave

Children