-
Okay regarding your second question i would use a third drop down list to keep things simble. set conditions to both (2nd and 3rd) ddl, hide one when your 1st ddl is blank and the other when it's not blank. for your 3rd you can then just use your secondary datasource.
Back to your first problem could you please post the structure of your ...
-
Yes you can do that of course. I guess what Greg ment is more that you cannot create any control out of nothing with infopath you can however append new childs to an existing node, see this for example for a repeating section:
string myRepeat = thisXDocument.DOM.selectSingleNode(''my:myFields/my:Result/my:Results'').xml;
IXMLDOMDocument oXml = ...
-
Hello again Mr Belgium,
you are actually not that far away from me. sitting here in Luxembourg, but anyway played around a bit and here is the solution for your first question:
that you can easier follow here my datasource structure:
dfs:myFields/dfs:dataFields/d:tblMachines
within this data source I have @Expr1 and @Expr2
Now double click ...
-
Oh sorry, it's not a value its the name of your Drop Down List control from where you select your article, may be my:field1 ?
-
This should work for you, use this within a rule of your dropdown list and you can fill a textbox with your unit price
xdXDocument:GetDOM(''LocalSales_Articles'')/dfs:myFields/dfs:dataFields/d:LocalSales_Articles/@Expr2[../@Expr1 = current()/../my:yourDDL]
-
Can you post your secondary data source? I guess it's an xml file right ?
-
try [@ArticleID = current()]/@UnitPrice at the end
-
HI Hans,
I think you have to use the current() function.
See below example, In my case I use a webservice to populate the values of a drop down list. When the user selects a name from this ddl the mail address is written into another text box. I use this statement within a rule of the ddl but your exbox should work as ...
-
Hi,
please refer to the follwing thread http://www.infopathdev.com/forums/topic.asp?TOPIC_ID=3970
Let me know if it helped.
-
Then I propose that you take care of the correct syntax in a previous step (e.g. when the web service writes the xml) cos I guess it will be easier to manipulate your ''date string'' with code rather than using data validation or rules within infopath.