Re: Validation Against A Single Instance of Data in a Repeating Table?

nkstrou — Mon, 20 Aug 2012 22:08:34 GMT

No, row # is not relevant and won't help, and the # of rows in tables O, P, & Q won't be consistent in the majority of cases. The common values are the 4 combobox values.

Is that clearer?

nkstrou

Re: Validation Against A Single Instance of Data in a Repeating Table?

Jimmy — Mon, 20 Aug 2012 17:09:41 GMT

So to be clear, do you want to validate the table Q rows against the table P rows based on position (i.e. match row 1 against row 1, etc.), or based on some other common value? Will tables O, P, and Q always have the same number of rows?

Validation Against A Single Instance of Data in a Repeating Table?

nkstrou — Sat, 18 Aug 2012 00:20:10 GMT

Hi InfoPathers:

My InfoPath 2010 filler form contains 2 repeating tables that I'll call tables O and P. Table O has a series of 3 cascading comboboxes, and table P has a series of 4 cascading comboboxes. Any entry in either table O or table P must have at least the first two comboboxes entered. I also have a set of 3 radiobuttons in each table called New, Existing, and Deletion.

My form contains an additional repeating table (which I'll called Table Q) that has 2 sets of cascading comboboxes that look up against the data entered in the comboboxes from tables O & P. Table Q additionally has a set of 3 radiobuttons called New, Existing, and Deletion.

I need to do some data validation whereby if a row in table Q shows as New or Existing, and the data that was entered in that row from Table O or P was a Deletion, then an error is triggered. In other words, if an item from Table O or P is a Deletion, then the only valid case in table Q should be if the row that looks up that Deletion item is also marked as a Deletion. Make sense?

On table Q, I have a validation rule on Tier4 of the cascading combos (called cboTblQ-C4) for the lookup against data from Table P for the following condition: optTblQ-XstNewDel not equal to "Deletion" AND cboTblQ-PC1 = cboTblP-C1 AND cboTblQ-PC2 = cboTblP-C2 AND cboTblQ-PC3 = cboTblP-C3 and cboTblQ-C4=cboTblP-C4 and optTblP-XstNewDel = "Deletion"

If I enter 2 line items in Table P where one is a Deletion and the other Existing, then create a row in Table Q that is Existing, and I pick the Existing entry from table P (which should be a valid case), the validation error turns on. In table P, I entered the Deletion item 1st and the Existing item 2nd, so to test whether it is matching on the first line item, I then entered the Existing item first and the Deletion item second and got the same results. Seems like it's matching against any row in table P that matches my conditions instead of against the row that matches the conditions I entered in table Q. I thought about adding a condition to the filters for my combobox cascades for optTblP-XstNewDel = optTblQ-XstNewDel, but that's too restrictive - I only need that to apply if optTblP-XstNewDel = Deletion.

Is there a way to do what I'm trying to do without custom code? Or alternately, to conditionally apply different filters to my cascading combobox lookups?

Thanks,

nkstrou

General

Re: Validation Against A Single Instance of Data in a Repeating Table?

Re: Validation Against A Single Instance of Data in a Repeating Table?

Validation Against A Single Instance of Data in a Repeating Table?