-
Then you are probably using the IP07 coding OM. In that case:
MainDataSource.CreateNavigator().SelectSingleNode("YourXPathHere")
-
Script: use XDocument
IP03 Managed Code: use thisXDocument
thisXDocument.DOM.selectSingleNode("/RootNode/XPathToField/my:hora_ent").text = hora;
-
var nodes=XDocument.GetDOM("pricing").selectNodes("/dfs:myFields/dfs:dataFields/tns:pricingResponse/tns:pricingResult/NewDataSet/Table"); //secondary datasource
for (var i=0; i < nodes.length; i++)
{
var curregion=nodes(i).selectSingleNode("REGION").text ; //fetch current ...
-
The User Role is evaluated when the form is opened. It is not stored anywhere and is not persisted across sessions.
You can either use code to set the user role (OnLoad) or you can make sure roles are order least to most restrictive when you create them. Roles let you use names and groups... take that into account.
It is sounding like you want ...
-
I have attempted to create a similar schema here using a Choice Group but am not seeing the same issue that you are seeing.
I notice from your schema that you are using either a database or web service. Is this the main DOM or a secondary DOM?
Lastly, will you pelase take a screenshot of the Edit Default Values dialog box and paste it in ...
-
Glad you got it working... but it seems as though there is unnecessarily a lot of extra work going on that shouldn't need to be.
I'm not familiar with Oracle, but the database should have some sort of a JOIN command that would allow you to get all the information you need with a single Web service, where it queries both tables, joining ...
-
That it is giving you a security error is what doesn't make sense.
Please also check that the object you are trying to get .Count on is valid and not null. This shouldn't give you a security error... but I'm at a loss for what could be going on. Doesn't appear that there would be any timing issues or anything.
-
Here's what I understand your problem to be: When you open a new form, there is an existing blank for in a repeating section/table that you don't want to be there. If that is the case, then this should be the correct approach. Make sure that you are unchecking the correct node. If you have a structure like
/Root/Table/Row/Fields
Then you ...
-
In the Changing event handler, the DOM is readonly.
In the Changed event handler, be sure to examine the e.Operation property to only process your code during the right operation (i.e. Delete, Insert, Value Change, etc)
-
In your form template (the designer), you need to edit the "Default Values" (Tools menu, or if using VSTO, Data menu).
From there you can tell the form to not insert that initial row (uncheck the appropriate box for the row node).