InfoPath Dev

Apparently, a secondary data source field cannot have data validation put on it, though, I am not sure why it is disabled.  

Aside from creating main data source fields and then copying it back using code or rules to the secondary data source, is there a better way?    I literally have hundreds of fields that would have to operate this way, and it would be a major pain to be forced into this method.  

What is the rationale behind only primary data fields needing validation?  Just because it is a secondary datasource, it doesn't mean that it will not be used for data entry, in fact, the majority of my data entry fields are in secondary data fields.

Perhaps someone from the Microsoft InfoPath team is reading this?   Hint hint.   ;-)

Secondary data sources are temporary. They are loaded in to view or to be used in the main schema but the data is not saved with the form.  That is why there is no validation, because they are typically read only.

So you would need to pull the data into your main schema and then manipulate it and submit it back if you are trying to create a form which manages these data sources.

 What are you trying to do? Give me the scenario.

Then I can maybe help you with possible solutions.

Here's the deal:

The secondary data sources are tied to an XML web service.  The XML web service also accepts the structure back to write back the data to the database, so it is a two-way secondary data source, if you will.

I know I can tie one xml query to the main data source, but I have multiple, so therein lies the problem.  I need to have secondary data source information displayed on the form and then the user can make changes.   I would rather not have to duplicate all the fields that are being used in the from (literally, several hundred) just to transfer information to and from these data sources.

Does this make sense?

Yep that makes sense.

Unfortunately I do not believe their is anyway around it.

Do you have both query fields and data fields generated in the data source?

Probably you would want to look at using code to do a bulk move of the data. I believe Greg has some blogs on this.

Well, the way around it is to enable the "Data Validation" button!

It seems as though secondary data sources are being used in ways that the developers did not originally expect, but I don't see why it would be such a big issue to make that available.   It sure would save me lots of time.

Anyway, I appreciate your response.   I was hopeful that there was a better way that someone figured out.

P.S.  Doing a bulk move is not an option.  There are to many "gotchas" with that method.