• Replies 3 replies
  • Subscribers 138 subscribers
  • Views 1275 views
  • Users 0 members are here
Options
Related

Deleted processing instructions being removed when doing a compare between versions

Mario Madunic

Hi,

I'm comparing v1 to v2 of a publication.

In a topic in v1 it has a processing instruction

The topic is versioned up in the v2 version of the publication

The processing instruction is removed from v2 of the topic

When I do a publish with comparison of v1 to v2, the processing instruction in the combined topic (with the compare PIs) is missing.

When I look at the export folder, v1 is correct and has the pi and v2 is correct also and is missing the pi.

But in the cmp dir the pi is missing altogether.

Is there a way to prevent PIs from being deleted in a compare when they have been deleted in the current version?

Mario Madunic
Rate translation
×
Suggest better translation
×
Parents

  • Hi Mario,

    Not completely sure what you are trying to achieve... comparing processing-instructions like <?oxy-... or <?xm-... during a publish compare?

    Do you expect a compare of processing-instructions to show up? I would be interested in the business purpose, if you don't mind sharing.

    The key thing is that the Compare engine (ChangeTracker) actually uses processing-instructions <?ish... to identify where inserts or deletes are. See TD14SP4 - IPublishComparePlugin - IshPublishCompare In turn nesting of processing-instructions is not allowed, so I can imagine that the compare simply ignores any incoming processing-instructions altogether.

    Appologies if I misunderstood your question.

    -Dave
  • in reply to Dave De Meyer

    We are using PIs for numbering of topics in a map and the numbering has to be predefined and does not change version to version. So when a topic is deleted in a map in v2, it still must be published using the PI that existed in v1.

    If a PI existed in one version and is deleted in a new version, it should still appear when a compare is done but in between the version PIs.

    PIs are not "nested" with a compare.
Reply
  • in reply to Dave De Meyer

    We are using PIs for numbering of topics in a map and the numbering has to be predefined and does not change version to version. So when a topic is deleted in a map in v2, it still must be published using the PI that existed in v1.

    If a PI existed in one version and is deleted in a new version, it should still appear when a compare is done but in between the version PIs.

    PIs are not "nested" with a compare.
Children
No Data