InfoPath Dev

I use those all the time - a lot of times, I'm working on forms that are in production. So, I like to preview my changes with existing XML - that way I can make sure I'm not creating any issues. Using Go To Next Error helps me find hidden validation errors. :)

Okay - this is an unfortunate issue with database bound forms - you added your field to the main data source - there will only be one instance of that field, even if you put it into your repeating group. You'd need to add it to the table. So you could add a field to your Art_Production table and walk through the data connection again to add ...

Use keyboard shortcuts to get the error info. Navigate to next field that has an error.CTRL+SHIFT+OGet error details for current field if it contains an error.CTRL+SHIFT+I

Okay, got it - you have nested repeating data. So - in the case of the helper field for Populated, it would probably need to go in the Art_Production repeating group, since that is what it refers to, right? The Production Complete date there? You want to show the ReqesterInformation group if any instance of the ProductionCompleteDate is blank? ...

Can you attach your form? Under the options tab.

Well - I was thinking along the lines of setting a field called "populated" to True, for example. So when I fill in the blank date, populated is set to true. Then, my conditional formatting could hide all rows where the Date is not blank and populated is not equal to true.

You are publishing it to a form library, correct? Sounds like a machine issue - if the users log onto a machine where the forms work for you, do they work correctly?

Hi - so you want to have conditional formatting on a table to hide rows where the date is not blank & then when the user fills in the date, still display the row? That's kind of a tough one. You could add a helper field of some kind to track whether the date was blank to start with....

Looks like you found this thread... but post back if it doesn't help!

Thanks for updating - sorry you had to set up a workaround. Kind of a baffling error scenario!