InfoPath Dev

The sum() function should certainly be taking negative values into account.  Has your experience been otherwise?  Perhaps you could to into specifics a bit more so that we might identify the issue?

From the Insert tab, you should be able to add a Hyperlink and set its properties to reference the hyperlink field.  Could you give that a try?

I'm guessing it would be something more like "../my:Field3" and not just "Field3", but why not just use an ordinary rule to do this?

I believe that MainDataSource.CreateNavigator.Select("//*[not(*)]") should provide you with an XPathNodeIterator that lists all of the leaf elements in the main data source.  It won't include attributes, but according to the documentation I linked you to, Get/SetNamedNodeProperty doesn't work on attributes.

InfoPath will produce an error like that if you try to add an XML node to the main data source that is not defined in the schema.  This has nothing to do with xsi:nil. If you're looking to set and retrieve metadata properties to arbitrary fields, perhaps the SetNamedNodeProperty/GetNamedNodeProperty API is the way to ...

As far as I can tell, SQL data sources do not distinguish between NULL and blank values.  Both are simply blank in the XML data. The QueryDB web service that's part of DBXL does allow drawing this distinction: null values are returned with an xsi:nil attribute in the XML, while blank values are simply blank, without an xsi:nil ...

So you're trying to show only the last row of the repeating table?  The following condition should work, though if you're using a browser form, you'll probably need a workaround for the position() and last() functions.Condition: position() != last() Formatting: hide

What is the actual error that you are getting?  Does your data source define RequestType as having an attribute named IsDirty?

I believe the OnAfterChange event should be available if you right-click the field in the data source task pane, but rather than going through the headaches of trying to make sense of some code, I would suggest using the pre-built functionality already available in qRules.  The latest version even has functionality to account for weekends and ...

Je pense que vous pourriez aussi utiliser les fonctionnes year(), month(), et day(): "year(Created) = " + date.Substring(0, 4) + " and month(Created) = " + date.Substring(5, 2) + " and day(Created) = " + date.Substring(8, 2)