-
Thank you. Yes, it looks like my:CoachingOp/my:SetArea/my:account is probably the right path. Did you try putting it all together with get-DOM() and everything?
xdXDocument:GetDOM("Systems By SysPrin")/Row[SysPrin = substring(xdXDocument-get-DOM()/my:CoachingOp/my:SetArea/my:account, 1, 8)]/State
my: might not ...
-
That's not your main data source. Could you change the dropdown there to show me the data source that includes my:account?
-
It seems you have edited your post, but in a previous version of your post I saw that you had the path in quotation marks (i.e. "/my:CoachingOp/my:SetArea/my:account"). It should not be in quotation marks.
I'm 95% sure it's a problem with your path to the my:account field. Could you post a screenshot of your ...
-
My mistake. That should be a colon before get-DOM(), not a hyphen:xdXDocument:get-DOM()But I'm dubious about the rest of that path. You need the to use the full path to the my:account node, e.g. my:myFields/yaddah yaddah/my:account, paying close attention to capitalization.
-
Thanks for providing a screenshot of the XML format. That's very helpful.
Placing a default value on the state field might be the way to go. Try setting its default value to this formula:
xdXDocument:GetDOM("Secondary data source name")/Row[SysPrin = substring(xdXDocument-get-DOM()/path to account name in main ...
-
There are a few problematic things in the code in your first post. Firstly, this line: MainSource.SelectSingleNode("/ns10:DirectImportDBForm/ns10:Items", ns);Will return a reference to an XPathNavigator positioned at the ns10:Items node (assuming it exists). It will not change the position of the MainSource ...
-
Qdabra's DBXL was designed precisely for this purpose. It's a server-based repository for InfoPath forms that can be easily configured to extract out the data you want into an SQL Server database. Once the data is there, you're free to perform queries and data pivots on the data from Excel or any other data processing ...
-
Well, you could add the condition "When Field1 is blank" to prevent it from being overwritten once it is set. For anything more complicated, you'll need to figure out some sort of form logic, involving buttons, etc., but it doesn't sound like you will need to use code.
-
That will give you several rows with read-only values, but the rows can still be removed :-). But perhaps that's good enough?
-
Rules only fire when their related field's value changes. If you've just "booted up the form," AccountId's value will not have undergone any change and Field1's value will be whatever its default value is.