-
I've never had this happen. Worst case, I suppose you could open your form library in Explorer view? The template is in the Forms folder.
-
Most likely you still have a rule pointing to the old data source. You can see the rules in the manifest - and the XPath is probably different between the two data connections. Save a copy of your form first, of course!
Oh, and you may also be able to use the Rule Inspector (Logic Inspector in IP 2007) to help find this, if you want to use ...
-
Generally the issue in a case like this is that the data is not actually equal. The data from the secondary data source may be slightly different than that which has been entered into the form.
However, this worked for you for setting field values based on a rule, so I'm surprised it isn't working as a filter. Are you getting all rows ...
-
Absolutely - you can use either conditional formatting to hide rows, or right click on the table and under the repeating table properties, in the display tab, add a filter there.
-
In the data source task pane, find your secondary data source that has the data you wish to display. Drag the repeating node with the data fields in it onto your form. You can then edit the repeating table to remove the columns you don't wish to show.
-
Sadly, InfoPath won't do this out of the box - copy data from one repeating data source to another, which it sounds like is what you want to do - copy repeating data from one data source into the main data source.
You have some options:
Just display the secondary data - this works if all you need is for users to see the data from your ...
-
Does it work in InfoPath Filler?
-
Only if you are going to save the templates as IP 2010 format. Your templates are currently IP 2007, and have qRules for 2007 injected in them - IP 2010 will open IP 2007 templates without an issue.
But if you re-save the template as IP 2010 format, you should re-inject.
-
The SetValue method takes a string - What is "ValueAsDouble" in your code above?
At any rate, if your field allows nulls, your issue may be that your aren't removing the nil attribute prior to setting it - are you getting an error message when you simply set your "my:Decimal" field to the string you are passing in?
-
Glad you found a way to do what you need - and thanks for updating the thread!