InfoPath Dev

Data validations are specific to the data element itself, not the control, so they will always be the same on every view.  Same goes for rules.  The only thing that is specific to the control is conditional formatting.  If you remove data validation from your field on a specific view, it actually removes it for that data element at ...

That's not normal - it should update when the template is changed.

Both posts say the same thing. I still contend that it's ridiculous for users to EXPECT to be able to manually type in people's names in reverse order with a comma and a space.  That is the least efficient manner of choosing a user and should not be the standard way of doing it.  They should be taught to use username or simply ...

You're just missing the filter part.  You have to say "set mymodel to datasourcemodel where datasourceasset = myasset."  Do that for each one.  That's how you specify which record to use.  It's critical that the asset# is unique... Oh, and you do that when you're in the screen where you choose the ...

1) That's confusing, because I was able to publish the form with that huge email view after removing the other views.  I figured it was based mainly off the # of data validation warnings, but if you still can't publish easily after changing those settings, then maybe it simply is a case of the overall file is too large (not file size, ...

Did changing all those data validation fields to "never" do anything, or did it still have trouble publishing? Is that last part working (submit to email DC), or do you still need to get it resolved?

Jess, I would recommend not putting your concat function directly within the data connection, because that causes it to be recalculated each time you submit.  This is ok if the data you're concatenating _never_ changes, but if it does, then your title will change at times.  It's best to create a filename data element (field) in ...

What part of this has to do with InfoPath?

Hold on a second.  You have a business requirement that is met by the technology, but you aren't going to use it, because users refuse to pay attention.  I don't think that's the right approach.  You don't just assume Joe is going to go to lunch and not check in his file.  You set a mandate that he MUST check in ...

I would think it's definitely a double-hop issue, since it only errors in the browser-form.  When you browser-enable the form, that introduces another hop in the data sequencing.  I've had this before where I was using a browser-enabled form to submit/read data to/from a database via a web service using a UDCX data connection ...