InfoPath Dev

Hello @Hilary-Stoupa, When I create a new form using "InfoPath Designer 2013 > New > SharePoint List" and add files using File Attachment, I can attach multiple files one under the other. When I create a new form using "InfoPath Designer 2013 > New > Blank Form" and want to add a file using File Attachment, I ...

Ah, I see. So, InfoPath has no rules-based way to add rows, unfortunately, and with a list form we don't have any of the options like adding default data rows and not using them. I don't know of a way to do this without third-party tools (i.e. the company I work for has a product called Qdabra Forms which has some functionality that would ...

Hi Hilary, Sorry for incomplete question. I'm attempting to create a repeating list form in SharePoint (not a library form). I want to add a secondary source that allows for the selection of multiple items, and based on those selections, I aim to create new rows. I hope I've communicated my objective clearly to you.

It would still result in the same error. The People Picker would provide the name, however, we still need the Standard ID. They would have to input both and hope they have the right information for both of them. We could get a cross of the name and the Standard ID. One still has to come from the Domain to keep the errors at a minimum!

Yuck - I don't know of a way around this, outside of using actual code to execute the query, and then in a catch statement, try again with the other domain. This Work Standard ID field - is that the value that is being concatenated to the domain for the query? Any way a people picker could be used for this?

This is just form rules on the Infopath form.

The error is from the actual server. There are multiple domains, so when I concat to \east, east is not the primary or is not one of the domains it errors out.

Is the error from the data connection? Sorry, I just didn't recall GetUserProfileByName returning an error from the data connection if the user didn't exist. I note this is under "code", are you using code behind for this, or just form rules?

I get an actual error and the user cannot move forward to fill out the rest of the form.

So - you get an actual error if the user you are querying for doesn't exist? Or is the data source just empty? I'd probably query first for "east", check the data source, and if there aren't any results, query for "west".