InfoPath Dev

But I need to report when the XML modified is greater than the SharePoint list item.  IE - the latest changes in the form, not the list.  From what I understand of the command from the qRules guide is that it does not work that way. I'll try the rule in reverse as you suggested. 

I tried this formula, with no success - my:Total != xdXDocument:GetDOM("Saved Pulls")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:Total[../d:ID = current()/my:PullID] I run a query of the SharePoint list first, but it still doesn't apply the formatiting.  Is there something else I need to do?  Shouldn't this ...

More questions, questions, questions . . . I have a table that a user submits, and another user reviews and adjusts the form accordingly (in a different view).  After the second user reviews it, the data is saved into a sharepoint list. The first user now has the option of editing the form again.  Is there an easy way to compare the ...

It works great!  What a nice feature.  Thanks!

Sure, I would love test it. 

Is it possible to filter the items that this command submits?  IE - if a repeating table row's field's value = zero, I don't want it submitted to the list.  I know I can delete the row first, but I don't want to go that route yet.  I still need the row in the form.

Wow.  I wish I would have read this thread about an hour ago.  Would have saved an hour of hair pulling.

OK, this is getting stranger.  I have mulitple views of the same table in my form view. One is using a preceding-sibling rule to just show single rows of a new category.  The other showing only rows that have a value that matches a field outside of the table.  Both of rules use a field inside of the table to compare.  This ...

Is there any difference between using a filter on the repeating table vs. using conditional formatting to hide rows of a repeating table?  Performance? 

I am using conditional formatting to hide rows in a large repeating table in the browser.  One table is using a simple field comparison to hide rows, the other is using a preceding-sibling condition to hide the rows.  In the client, the filtered tables work great.  No delay, no latency, etc.  In the ...