InfoPath Dev

I have a table with a unique index constraint that works great 98% of the time. Occasionally, I will get the duplicate key error when submitting - but the row is definitely NOT in the table. If I make a small change to , say a note field, in another row and submit that THEN go back and add the row IP complained about previously then the row is ...

Can you clarify where the following should be accomplished..."So put a rule on the ID field to set the date (or whatever) field based on a condition...."? Should the rule be attached to the ID field in the data connection, and should that be an action that set field value of the Date of Last Inspection -if blank- to whatever text I want ...

The problem with the secondary data is when you query it, each row needs to be evaluated. The rule on the building number field would only work to set every single row to the same value - not what you want. Instead, "repurpose" another field in the secondary data connection. You are probably not using the ID field, right? So put a rule ...

I'm an InfoPath simpleton. Yes, I'll need you to provide more detail, please. Let's assume I'm a five year old; now, tell me how and where, again.

Hi Curtis, To get this technique to work in a repeating table requires an xpath that remembers the current() row that you are on (assuming you want to have a condition for the previous column). Let's say you have three columns and you want to condition the value for column two on column one. You would use the same kind of rule for the ...

Worked like a charm. Now, can I do the same for a similar field in a repeating table? The table data is coming from a secondary connection, activated by the same building number entry process as the previous post.

Sure. In the same rules you are using when the building number is entered, have the last rule check to see if the Date of Previous Inspection field is blank, and if it is, set the field's value. I wouldn't set a date field to text, myself - but if your date isn't actually a date, it should be fine. Or use another field.

I have an InfoPath form the users can upload to a SP Library. A field on this form is 'Date of Inspection'. Currently, when a new form is uploaded I get an email, from a workflow email I created. From this email I identify the 'Date of Inspection', I then manually open a SP List, associated with the InfoPath form, and update the ...

This may sound like the same issue, but it's not. Can an InfoPath Date field be self-aware? I have a form that has a field called Date of Previous Inspection. The data for that field comes from a SP list column of the same name. The field, as well as several others, auto-populates (and it does work right now), whenever the user enters the ...

Yup, you got it. :)