Excluding xml elements in this script ...

This script (Green4ever) insert "\r" after element:
var myDoc = app.activeDocument;
var inddRooElement = myDoc.xmlElements.item(0);
var xPathElements = inddRooElement.evaluateXPathExpression("//*");
var elementCount = xPathElements.length;
for(var eId=0; eId<elementCount; eId++){
var thisXpathElement = xPathElements[eId];
thisXpathElement.insertTextAsContent("\r", XMLElementPosition.AFTER_ELEMENT);
alert("Done");
But, I need some xml elements are excluded.
How I can exclude some XML elements?
How do exclude all items that have in the tag "<p>"?
Thanks...

Try:
var xPathElements = inddRooElement.evaluateXPathExpression("//*[not(ancestor::p)]");
or, if you want to exclude p as well,
var xPathElements = inddRooElement.evaluateXPathExpression("//*[not(ancestor-or-self::p)]");
Jeff

Similar Messages

Create XML element without closing tag using Visual C++

I know how to create xml element with closing tag (using WriteStartElement and WriteEndElement methods)
<tag id="1234">
</tag>
but is there a way in Visual C++ to produce xml element like this
<tag id="1234"/>
i.e. without closing tag?

Hi adamay,
Please refer to this thread.
http://stackoverflow.com/questions/8182245/create-xml-element-without-closing-tag-using-xslt
I think you could try the way of write your own class derived from XmlWriter.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Rename or Tag Element for particular Xml Element.

hi,
How to rename or Tag Element for particular Xml Element using Java Script.
eg)label to labels
Thanks in advance
Smile

Hi,
       Thanks a lot Jeff...
        I'm doing a huge program with lot of tasks. While doing that,my mind didn't strike to check if the tag is not already exist, then only to create new tag... Thanks for all of the indesigner experts for their replies...
I used the following codes with ur idea.
                    var renamewith = textbox1.text;
                    try
                        alert(app.activeDocument.xmlTags.item(renamewith).name);
                        if(app.activeDocument.xmlTags.item(renamewith).name)
                           var testTag = app.activeDocument.xmlTags.item(renamewith);
                    catch(e)
                        var testTag = app.activeDocument.xmlTags.add({name: renamewith});
With Regards,
Vel.

I need the XML elements appear in different paragraphs ... Could do this with a script?

I need the XML elements appear in different paragraphs ...
Could do this with a script?
Thanks...

You can use this / Puedes usar esto
insertTextAsContent("\n",XMLElementPosition.beforeElement);
// or
insertTextAsContent("\r", XMLElementPosition.afterElement);
Necesitaria mas información,

Hiding XML elements in the structure view – scripting influence to the structure view?

Hi
Is there a way to hide specific XML elements (really the elements and not the attributes) in the structure view?
I am asking this question to know if it is possible to influence the structure view by scripting.
Many elements are indeed used as a kind of help for constructions which have nothing to do with the actual contents especially in the case of tables.
You inflate the the structure view unnecessarily and the author will lose track of the real contents. It would be nice if there was a possibility to hide those help construction elements.
Thank you for any hints.
Regards
Apollo102

Hello Apollo,
There is a way to hide elements from the Structure View (one such method is offered by the free AXCM plug-in). What happens when you use AXCM (or other methods to hide elements) is that the elements get wrapped into hidden content. This might make the structure view less complex for your authors, but has a number of disadvantages and dangers.
1. The structure is normally invalidated, as the helper elements are usually required.
2. Accidentally deleting hidden content may make the invalidation permanent and render your documents useless.
It is NOT good practice to hide elements from authors in the structure view. Instead, you should either teach authors about the structure, or let them work in the Author View while adding sufficiently clear formatting to show them the underlying structure. In some cases, it might be better to create an authoring structure which is automatically transformed into the required full structure using an XSLT or other processing step. I have created a couple of such environments and they work fine. It just depends on the difference between the structure required for further processing and the structure that would be optimal for your authors (which in turn depends on the level at which your authors are experienced in working with structured content).
I hope this helps you solve your problem without having to tweak the structure view.
Kind regards
Jang

How to find out the page number of an xml element

Hi everybody, sorry for my very bad english (french guy! logical). I hope you see what I'm looking for.
I'm scripting (javascript) an exporting script of every articles from a multi-pages indesign script.
In fact I could have one or more article in one file, every one of them is on an separate xml element. for each I have to export an xml file named with, first, the page number where appears the xml element, second, the number of exported article.
I'm success the second purpose, but not the first.
Someone have an idea ?

Try this,
var myDoc=app.activeDocument;
var root = myDoc.xmlElements[0];
var docTag = root.evaluateXPathExpression('//doc');
for(i=0; i<docTag.length; i++)
    var docPos = docTag[i].insertionPoints.lastItem();
    var docFrame = docPos.parentTextFrames[0];
    var docPage;
    try
         docPage = docFrame.parentPage;
catch(e)
        docPage = docFrame.parent.name;
    alert(docPage.name);
Vandy

[CS3] [JS] add XML Element to Insertion Points

hi list,
i'll do some text parsing in indesign cs3 intended to add some xml elements to my document.
i just wonder why i can't markup an insertion point. is the following approach correct? The code works fine, only the return value (stored in the _xml variable) is not the new element but the parent element. The same code works without using the insertion point (marking up the text object [xmlElements.add(_dokument.xmlTags.item("index") , erg[0]))] ).
Any ideas or thoughts?
var _dokument = app.activeDocument;
main ();
// ** main ()
function main() {
//Set the find options.
app.findGrepPreferences = NothingEnum.nothing;
app.changeGrepPreferences= NothingEnum.nothing;
//find any string encloased by @
app.findGrepPreferences.findWhat = "@.*?@";
erg = _dokument.findGrep();
while (erg.length > 0) {
_xml = _dokument.xmlElements[0].xmlElements.item("text").xmlElements.add(_dokument.xmlTags.item( "index") , erg[0].insertionPoints[0]);
erg[0].contents = "";
erg = _dokument.findGrep();

hi dave,
gui testing is always a good idea :-) but in this case the behaviour is different:
your observation is correct (anyway at least a strange behaviour compared to any xml editing tool i know == how adobe intended to insert an empty element?), tagging in the gui a tagged insertion point tags the whole story.
in the script a new element is added but the return value is the parent element (the xmlElement of the whole story).
this causes a problem when i add an attribute (the intention of the above script is to add references) which is added to the parent element.
gregor

Remove xml element using JS[CS3]

Hi, I have an xml structure where i want to remove some paritcular element named "extlink".
I do have one script with me but it doesn't wipe out all specific xml element from structure.
var myDoc = app.activeDocument;
var foundtext = 0
Query_Remove (myDoc);
alert ("You have removed " + foundtext + " " +" Link !!")
exit (0);
function Query_Remove(elm)
try
for(var i=elm.xmlElements.length-1; i>=0; i--)
     if((elm.xmlElements[i].markupTag.name == "extlink") && (elm.xmlElements[i].xmlElements[0].markupTag.name == "http"))
    var Store_CitAttri = elm.xmlElements[i].xmlElements[0].xmlAttributes.item("c_style").value;
     if(Store_CitAttri == "URL")
      elm.xmlElements[i].remove();
     foundtext = foundtext + 1;
   Query_Remove(elm.xmlElements[i]);
catch (e){
Some time it skip the element from all figure captions and some time from body text and some time it works perfectly
Could any one figure it out why this script behaviour is not consistent as i am new to scripting and not getting any idea about this.
Thanks
Mac

Okay, after peering over your code and trying a few things out I see one immediate problem and one possible improvement.
The problem lies in this:
1. if condition is true, remove item
2. check recursively
The problem is .. if an item is removed, the following recursive check will always fail. However, the entire loop is wrapped into a try..catch, so InDesign will not alert you that it failed. Instead, it will continue with what's after the loop, exactly because the try..catch is around the entire loop!
Change the loop code to this
if((elm.xmlElements[i].markupTag.name == "http") && (elm.xmlElements[i].parent.markupTag.name == "extlink"))
    var Store_CitAttri = elm.xmlElements[i].xmlAttributes.item("c_style").value;
    if(Store_CitAttri == "URL")
      elm.xmlElements[i].remove();
       foundtext = foundtext + 1;
       continue;
Query_Remove(elm.xmlElements[i]);
so the recursive checking is skipped. You can also remove the entire try..catch block, as this may hide additional errors ...
The improvement is: as I started reading this thread from the top again, shouldn't you be removing the "extlink" items, rather than just the "http" ones inside?
If so, remove the parent of the found item (which is always the "extlink"):
      elm.xmlElements[i].parent.remove();
-- and, as this will break the loop (because you just removed the set of elements it was working in!), replace 'continue' with 'return'.
Hope this helps

Missing XML Element when using asset from library

This is not really a scripting question but I seem to be unable to find any regular ID forum and it has something to do with a scripting workflow I established for a customer.
A script places an asset from a library onto a document and then (amongst other things) imports some XML file.
The asset in the library consists of a number of textframes and has the structure e.g.:
article
box
box
Now the customer needs new templates (that is assets in the library) and we cannot produce them anymore. It seems that as of CS 3 5.0.4 Adobe changed the behavior of the library. Dragging e.g. two box-tagged boxes with an article parent XML into the library leads to an asset without the article element. Can someone confirm this? And more important is there a reason to it? Or is there a way to configure the behavior?
I guess I could create a parent xml element by script after placing the element but then I would need to redo all existing libraries.
Thank you,
Ralf

while( testIterator.hasNext() ) {
   Element testElement = (Element)testIterator.next();
   String code = testElement.getChildTextTrim("code");
    if( null == code ) {
           continue;
   String analysis= testElement.getChildTextTrim("analysis");
   //same for description
}

Create XML Element Tag BasedOn Found Character Style

Hi,
Good Day!
Basically I want to search only for character styles that contains "ntb-", that is why it is hard coded in my searchString variable.
Although I was able to create XML tag based on selected character style, but it will always add/insert at the end of the parent XML element.
Can anyone could help me how insert/add that element at the insertion point where the text is found?
Thanks,
--elmer
var myDoc = app.documents[0];
myDoc.viewPreferences.horizontalMeasurementUnits = MeasurementUnits.POINTS;
myDoc.viewPreferences.verticalMeasurementUnits = MeasurementUnits.POINTS;
var charStyles = myDoc.allCharacterStyles;
var foundStyles = Array();
var searchString = String();
    searchString = 'ntb-';
var tempName = String();
var tempName1 = String();
for(var i = 1; charStyles.length > i; i++){
   tempName = charStyles[i].name;
   tempName1 = tempName.toLowerCase();
   if(tempName1.indexOf (searchString.toLowerCase()) != -1){
       foundStyles.push (tempName);
var myDialog = app.dialogs.add({name: "Convert Footnote Character Styles to XML Tags",canCancel:true});
with (myDialog) {
    with (dialogColumns.add().borderPanels.add()) {
        with (dialogColumns.add()) {
            staticTexts.add({staticLabel: "Character style to search : "});        }
        with (dialogColumns.add()) {
            selCharStyle = dropdowns.add({stringList: foundStyles, selectedIndex: 0, minWidth: 175});
var dialogShown = myDialog.show();
while (dialogShown) {
    if (selCharStyle.selectedIndex == 0) {
        alert("Must have at least a character style to search!");
        dialogShown = myDialog.show();
        continue;
    } else {
        insertXMLTags(selCharStyle.stringList[selCharStyle.selectedIndex], selCharStyle.selectedIndex, "0");
        break;
myDialog.destroy();
alert("Finished!");
exit();
function insertXMLTags(cStyle, cStyleIndex, ip) {
    var myFinds = searchStyle(cStyle, cStyleIndex);
    for (i=myFinds.length - 1; i>=0; i--) {
        var myIP = myFinds[i].texts.item(0).insertionPoints.item(0);
        var myParentXML = myIP.associatedXMLElements[0];
        var myChiidXML = myParentXML.xmlElements.add ( cStyle );
        myChiidXML.contents = myFinds[i].contents;
        //set the selection
        app.selection = myFinds[i].texts.item(0);
        //remove the selected text
        myFinds[i].texts.item(0).remove();
        Utility Functions
function searchStyle(cStyle, cStyleIndex){
    var myFinds;
    // if script version is for Indesign CS2
    if (app.scriptPreferences.version < 5){
        app.findPreferences = NothingEnum.nothing;
        app.changePreferences = NothingEnum.nothing;
        myFinds = myDoc.search(undefined, undefined, undefined, undefined,
        {appliedParagraphStyle: pStyle, appliedCharacterStyle: cStyle});
    // else, for CS3 and CS4
    }else{
        //Clear any existing find/change settings
        app.findTextPreferences = NothingEnum.nothing;
        app.changeTextPreferences = NothingEnum.nothing;
        // set character or paragraph style to search
        if (cStyleIndex != 0){
            app.findTextPreferences.appliedCharacterStyle = cStyle;
        //Set the find options.
        app.findChangeTextOptions.caseSensitive = false;
        app.findChangeTextOptions.includeFootnotes = true;
        app.findChangeTextOptions.includeHiddenLayers = false;
        app.findChangeTextOptions.includeLockedLayersForFind = false;
        app.findChangeTextOptions.includeLockedStoriesForFind = false;
        app.findChangeTextOptions.includeMasterPages = false;
        app.findChangeTextOptions.wholeWord = false;
        myFinds = myDoc.findText();
    return myFinds;

Here is a way you can find any field.
Download the current template.
Open it in word and go to the line that you are interested in.
The blanket PO# will be a field. Right click on it and go to properties. You will see the xml element there.
Hope this answers your question,
Sandeep Gandhi

Selecting the content of XML element CS3(JS)

Hi
I am trying to select the whole content of XML Element.
I am trying like this
app.activeDocument.xmlElements[i].select();
But it is not working.
Regards
Suresh

A few hints:
Perhaps your variable
i i
is not defined. If that's the case, give up trying to write code for this complicated job! XML is not the easiest part of ID to begin with. Starting with uninitialized variables and flagging that as an error (and complaining about that in a forum) is a beginners' blunder.
If I run your script line with i set to 0, the first element of my XML structure is selected. I can see with my own eyes it works, because I have the XML Structure pane in ID open. If I click on the 2nd element there and run your script line, the top (= 0th) element is selected. Perhaps you didn't open the XML Structure view so you did not see it worked after all. Or perhaps you expected something
i else
to be selected -- the text content, maybe -- so you tag it as "error". That's a misinterpretation of what the XmlElement object is. Understandable, but still not an error. You can have lots of XmlElements without any text or other object associated. If it was your intention to select whatever the xml element contains, try working with the property 'xmlContent'. From its description I gather that sort-of does this alternative interpretation, i.e., you can select the
i text
which is pointed to by the element. Untried. But do read on.
If I run your script with i = 1, I
i do
get an error, and it's perfectly valid too! "Object is invalid" -- well, of course it is. There is no other XML element at that level. An app.document.xmlelements entry always points to the
i root
of the XML, and you can only have one. Perhaps you expected #1 to be the next sub-element. Well, not so in the ID implementation -- as usual for almost all XML based structures, it's a tree. The "next" element is xmlElements[0].xmlElements[0], which you can check by changing your line to
>app.activeDocument.xmlElements[0].xmlElements[0].select();
and verifying the 2nd element from the top is selected in the XML Structure view.

Imported XSLT cannot create attributes for generated XML element

I have two xslts. One imports the other.
The imported xslt creates XML elements with attributes and this XML is stored in a variable in the main stylesheet
If I perform the transformation with JRE prior to 1.6.0.18 then all works fine
If I use 1.6.0.18 or 1.6.0.19 then the attributes aren't added.
If I add attributes in the main xslt it works fine or if I output the element directly instead of first storing it in a variable then it also works fine.
Problem seems to be when you try to add attributes from an imported stylesheet and store the generated element in a variable.
Below two stylesheets to illustrate :
First MainStylesheet.xsl
<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:exsl="http://exslt.org/common"
extension-element-prefixes="exsl"
exclude-result-prefixes="xs">
<xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes" />
<xsl:import href="innerstylesheet.xsl"/>
<xsl:template match="/TestData">
<xsl:variable name="generatedElementXml">
<xsl:call-template name="generateElement">
<xsl:with-param name="s">testValue</xsl:with-param>
</xsl:call-template>
</xsl:variable>
<xsl:for-each select="exsl:node-set($generatedElementXml)">
*** GeneratedElementXML {<xsl:text>
</xsl:text><xsl:copy-of select="*"></xsl:copy-of>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>Next innerstylesheet.xsl
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:exsl="http://exslt.org/common"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
extension-element-prefixes="exsl" >
        <xsl:output method="xml" version="1.0" encoding="utf-8" indent="yes"/>
        <xsl:template name="generateElement">
                   <xsl:param name="s"/>
                <TestElement testAttribute="$s" />
        </xsl:template>
</xsl:stylesheet>The result output by jres before 1.6.0.18 is :
<?xml version="1.0" encoding="UTF-8"?>
               *** GeneratedElementXML {
          <TestElement xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" testAttribute="testValue"/>
               }          The result output by jres since 1.6.0.18 is :
<?xml version="1.0" encoding="UTF-8"?>
               *** GeneratedElementXML {
          <TestElement xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
               }          Note : the 'testAttribute' attribute is missing

Have found the difference in the code
In both JRE1.6.0_17 & JRE1.6.0_18, the class 'com.sun.org.apache.xalan.internal.xsltc.dom.AdaptiveResultTreeImpl' has the following method
public void addUniqueAttribute(String qName, String value, int flags)
        throws SAXException
        addAttribute(qName, value);
    }In JRE1.6.0_17 the next method is
public void addAttribute(String name, String value)
     if (_openElementName != null) {
         _attributes.add(name, value);
     else {
         BasisLibrary.runTimeError(BasisLibrary.STRAY_ATTRIBUTE_ERR, name);
    }In JRE1.6.0_18 the next method is
public void addAttribute(String uri, String localName, String qname,
            String type, String value)
     if (_openElementName != null) {
         _attributes.addAttribute(uri, localName, qname, type, value);
     else {
         BasisLibrary.runTimeError(BasisLibrary.STRAY_ATTRIBUTE_ERR, qname);
    }Note - the addAttribute method has additional parameters in JRE1.6.0_18 but the call from addUniqueAttribute wasn't updated.
So in JRE1.6.0_18 addUniqueAttribute actually invokes the following method in the base package com.sun.org.apache.xml.internal.serializer.EmptySerializer
public void addAttribute(String name, String value)
        aMethodIsCalled();
void aMethodIsCalled()
        // throw new RuntimeException(err);
        return;
    }and as you can see this does nothing. Hence the fact that the attribute isn't added.

How to map more than one xml element with some Paragraph in a Text Frame

Hi friends,
I am new in InDesign Java Scripting and I have to place or map, more than one xml elements of different parents, into one textbox. Is it possible through JavaScript? Can anyone help me in this because I have no idea how it should work and it urgently required.
Thanks in Advance

I had answered to you already in your first post: the short answer is that it's not possible on the same text box unless you assign a common ancestor of these two "parents" item. That's not a question of scripting, it's the way Indesign handle the XML with the layout. Import a xml in Indesign and drop tags to page item. What you can do manually is quite representative of what can be done through scripting.
If you assign this anscestor to the text frame, you have to expect that all text child items will be displayed in the text frame (including the text of all the child of the two "parents" and all the other parents/childs that could be under the common ancestor). Having a XML that is designed for Indesign usage is pretty much inevitable if you are doing anything "serious".

XML Element of XML Element of XML Element (and so on...)

Here is my XML data (shorted, in a file myFile):
<LiveData>
<Voltage>
<Total>
<VoltageNow>1052</VoltageNow>
</Total>
</Voltage>
<Power>
<Total>
<PowerNow>345</PowerNow>
</Total>
</LiveData>
I would like to get the VoltageNow and PowerNow values, but the following script does not work:
tell application "System Events"
set elem1 to XML element 1 of XML file myFile /*<LiveData>
set power to XML elements of elem1 whose name is "Power"
set total to XML elements of power whose name is "Total"
set powernow to value of XML elements of total whose name is "PowerNow"
end tell
Error: System Events got an error: Can’t make {} into type string.
BTW, I don't want to use XML Element X because the order may change.
What is the correct method to traverse these elements to obtain values?

AppleScript can handle the strings, but the System Events XML Suite doesn't work with text strings - it deals with the XML objects, which have name and value properties. The handler can be modified to show the names of an element, but it is just designed to work with the XML Suite.
The contents of an XML file is just text, so you can forgo System Events and just use regular text manipulation statements, or use another tool such as the Satimage XMLLib osax, which is much more robust and does include commands to display the XML object as a string.
By the way, my original handler was designed and tested in Leopard, but I discovered a Snow Leopard bug that alters the way it returns array/list contents. The following script has changes that return the functionality, in addition to a dialog handler that will display lists:
<pre style="
font-family: Monaco, 'Courier New', Courier, monospace;
font-size: 10px;
font-weight: normal;
margin: 0px;
padding: 5px;
border: 1px solid #000000;
width: 720px; height: 340px;
color: #000000;
background-color: #DAFFB6;
overflow: auto;"
title="this text can be pasted into the Script Editor">
on run -- example
set XMLFile to (choose file without invisibles)
show("element value:", (getXMLElement from {XMLFile, "LiveData", "Voltage", "Total", "VoltageNow"}))
end run
to show(label, something)
show an alert for something, formatting lists and records
parameters - label [text]: the alert text
something [mixed]: an item to put in the alert message
returns nothing
if something is not in {null, missing value} then
try -- show the message
if (class of something) is in {list, record} then (something as number) -- force an error
display alert label message (something as text)
on error errorMessage -- lists and records don't format very well, so cheat
set {here, there} to {(offset of "{" in errorMessage), -(offset of "}" in (reverse of text items of errorMessage) as text)}
display alert label message text here thru there of errorMessage
end try
else
display alert label message "*null or missing value*"
end if
end show
to getXMLElement from XMLItems
get the specified element from a simple XML structure by name or index
the number of items is not fixed, but must be at least 2 (the XML file and an XML element)
parameters: XMLItems [list] -
item 1 [text]: the XML file path (Finder or POSIX)
item 2 [mixed]: the XML element name or index (names are case sensitive)
item(s) 3+ [mixed]: sub item(s)
returns [list]: value of the element
try
if (count XMLItems) is less than 2 then error "getXMLElement handler: item list contains too few items"
tell application "System Events"
set theXMLData to contents of XML file ((the first item of XMLItems) as text)
-- get text of theXMLData
set theXMLElement to XML element 1 of theXMLData -- start at the root element
repeat with anItem in rest of XMLItems -- add on the sub items
set anItem to contents of anItem
try
set anItem to anItem as integer -- index number?
end try
set theXMLElement to (get XML element anItem of theXMLElement)
end repeat
try -- return the element(s)
-- return name of XML elements of theXMLElement
set theResult to value of theXMLElement -- SL built-in result variable does not get set
if theResult is missing value then error -- SL does not error on empty or missing value
return theResult
on error errorMessage number errorNumber -- the element is empty, or a list of items
log errorMessage
return value of XML elements of theXMLElement
end try
end tell
on error errorMessage number errorNumber
log errorMessage
-- return null
error "getXMLElement handler: element not found (" & errorNumber & ")"
end try
end getXMLElement</pre>

Delete xml element not used in document

Hi,
If you have a number of texts tagged with an xml element and then delete the text, the element still exist in the structure.
You can see the element still connected to a text, by the blue diamond on the element symbol.
But i want do delete the elements that have no connection to texts, but cant find the right property to look for.
In Java script CS4.
Anyone knows?
/Mikael

If the (text) element is unplaced, its parentStory will be an XmlStory rather than a Story.
So try:
var elements = app.activeDocument.xmlElements[0].xmlElements.everyItem().getElements();
for (var i = elements.length - 1;i >= 0;i--){
if(elements[i].parentStory.constructor.name === "XmlStory"){
elements[i].remove();
This is untested. If you have tagged graphics frames it will need to be modified to not error on those.
Jeff

Excluding xml elements in this script ...

Similar Messages

Maybe you are looking for