-
it seems the path of the field is different, go to design mode in your form. In design tasks, click Datasources, go to your field and right click and select copy xpath, paste the same as an argument to root.SelectSinglenode(XPath, this.NamespaceManager).SetValue(formName)
-
set rule opening to set the value of fieldA to username()
to do so
open your template go to
tools -> form options -> open and save -> Rules
-
yes if the data entered is invalid, the filed border will be dotted red and it will carry the tool tip
-
[quote user="mark-scott"]root.SelectSingleNode(
"//my:formName", NamespaceManager).SetValue(formName);[/quote]
change it to
root.SelectSingleNode("/my:myFields/my:formName",NamespaceManager).SetValue(formName);
-
you can use reply -> options -> add/update to attach files here
you can mail me at qazianis303@gmail.com
-
yes workflows can only access promoted fields only (unless you go for xml reader, that will require of coding and i dont recommend that).
well have some rules on opening of the form, that checks if the person opening the form belongs to the department that should currently edit the form. if so allow him/her to edit else change view to a readonly ...
-
can you attach your form (xml) which gives error, and your form template
-
your this code seems to be good, just verify that the field path is valid, and use this.NamespaceManager instead of NamespaceManager.
Also you can open the form in notepad and check whether FCR_fldrURl contains a valid location and file name.
-
an easier way will be to automatically update the forms on publishing
to do so open your form template
go to tools -> form options -> versioning
in the version upgrade field select "Automatically upgrade existing forms"
on next publish all forms will be automatically upgraded
-