-
First verify that GetDOM is actually returning an object.
Then see if you can select the root node. Then then next one down, etc.
Troubleshoot this way to figure out where the source of the problem is. Find out where the selections are failing. . . is it the data source object itself, or the XPath?
-
First question: Will monthlyExpeses actually equal SelectedemployeeDepartment, or should you be comparing employeeDepartment against SelectedemployeeDepartment? I'm guessin the latter.
Sounds like you need something more like:
/myFields/datafields/d:TOSS[employeeDepartment = current()/SelectedemployeeDepartment]/@monthlyExpenses
Of course, I ...
-
This is an unfortunate limitation. To get around this you will need to have a web service between your form and your database.
-
You can call into the task pane from managed code, but it will require Full Trust on your form because you are calling from managed to unmanaged code. If you go in the reverse (unmanaged to managed -or- task pane to form) then the Full Trust requirement does not exist.
-
When you open the new form via code, it returns a handle to the XDocument object of the form you just opened. You can use that XDocument object to populate data from the existing form into the new form.
-
What event handler are you using in your code? Some event handlers are run while the DOM is in readonly mode.
-
That is the correct way to get the rounding. However, if you were able to set a SharePoint column to use 2 decimals, then you probably don't need to have the extra field with the rounded results any more. Is that the case?
You should be able to specify that you data connection not allow overwrites. At least I believe that you can.
-
Glad to help. Keep that OM Reference in mind when you get stuck. It is very useful. I find that I refer to it frequently.
-
It sounds like you have a Web service that returns a certain schema, but in the case of an error it returns a different schema. This is not possible.
Two solutions:
1. Create a combined schema for success and failure. That way no matter which XML you return, the schema will match.
2. Use a try/catch block and if there is an error, query a ...
-
You might get negligibly better performance with rules. Chances are you won't ever notice.