-
All of this is going to be very hard with just InfoPath and SharePoint, I'm sorry to say. You are really going to have to get the repeating data out of the form in order to do things like analyze and prioritize it.... but submitting data from InfoPath to a SharePoint list requires code or third party tools... I wonder if you could use a ...
-
You might want to drag the fields bound to the people picker onto a form to confirm this - but I wonder if the display name field will be blank if the account id doesn't resolve. Probably worth checking. :)
-
What are the data types of the fields that will be getting values when the transformed data is inserted into the main data source? Are they all string? any attributes? If anything requires the xsi:nil attribute if blank, that could be the issue.... Another option is to take that transformed XML, paste it into an XML you can preview with, make sure ...
-
Ah hah! - and so you know - this is the thing with default values if you decide to use this technique on an existing form, already in production - if you were to add a new repeating group w/ defaults to your form, and opened existing XML with it - you'd see the same result. Just something to be aware of. :)
-
You should be able to use REST then - although your server admins may need to modify some settings for your browser form to query SharePoint web services.
A web search for InfoPath Excel REST returns a lot of results - you may want to try that. Here are a ...
-
Can you send me a copy of the form, or attach it here? I'll take a quick look & see if I can see why it is being stubborn.... The results in your second table are what you see when you open a new, blank form?
-
You are so welcome - when working with XML, XSLT is wonderful magic. :)
-
Make sure all database tables have a primary key. Then walk through the data connection again in your form.
-
I would like to point out that I might be an idiot. :) You know I mentioned your "my" namespace was off? Well.... it probably isn't off for your form, but was off for my sample form. In your transform you are using in your "real" form - fix that my namespace to use the correct URL. I'm gonna go die of shame now.
-
I made a few changes to your transform in the attached sample file (the "my" namespace didn't match the "my" namespace in your form, and we don't need a for-each, we can use apply-template instead) - but I think I named everything the same in this sample & you'll be able to apply the same command to your form. I ...