InfoPath Dev

I have created a SharePoint 2013 Infopath form for Team Input. The first entry is their Work Standard ID Number. From that entry, I use a "GetUserProfileByName" data connection to the Soap Server. I need the form to bring me back the name of the person who owns the Standard ID Number. This works using the following concatenation: concat("i:0#.w|east\", Work Standard ID (field). This brings me the person's name who owns the Work Standard ID - until I reach a person who resides in a different domain such as "i:0#.w|west. Is there a way to string the concats to look in both domains, or "stack" them to check for both? I need the form to bring back the name and right now it just errors out because it is only doing a concat on one of the domains. Please assist! Thank You!!

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".

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

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?

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.

This is just form rules on the Infopath form.

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?

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!