Quantcast
Channel: Adobe Community : All Content - LiveCycle Designer
Viewing all articles
Browse latest Browse all 5571

RE breaks Floating FIelds in Fragment in Master Page

$
0
0

I have a fragment in a master page, which has a number of floating fields in it. The form works fine. However when I apply reader extensions in Acrobat, the form begins throwing errors in the ColorFieldsValidation designer generates. (line 42)


if (oInvalidNode.errorText == "") {


// Validation Succeeded


// Revert the appearance to its original state


var oBorder = sClassName == "field" ? oInvalidNode.ui.oneOfChild.border : oInvalidNode.border;


oBorder.parent.nodes.remove(oBorder);





// Remove the tool tip if it wasn’t originally specified


var sSOM = oInvalidNode.somExpression;


sSOM = sSOM.replace("xfa[0].form[0]", "xfa[0].template[0]");


console.println("sSOM" + sSOM);


var oOriginalNode = xfa.resolveNode(sSOM);


var oOriginalAssist = oOriginalNode.assist;





if (!oOriginalAssist.isPropertySpecified("toolTip")) {



var oToolTip = oInvalidNode.assist.toolTip;



oInvalidNode.assist.nodes.remove(oToolTip);


}

}

 

I added a console.println, and noticed the error is because the document is referencing a form object that does not exist

 

sSOMxfa[0].template[0].Form1[0].#pageSet[0].FirstPage[0].SupportSection[1].CurrentPageNumber[0]

 

oOriginalNode is null

42:1

TypeError: oOriginalNode is null

42:1

 

I've checked and double checked, there is no duplicate SupportSection fragment in my pages or master pages. What could be causing this? Is it a bug? Using Designer ES4.


Viewing all articles
Browse latest Browse all 5571

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>