InfoPath Dev

We are in the process of migrating to SharePoint 2013. We have setup an interim server where we are testing everything to make sure we work out all the bugs prior to the migration going live. We have Qdabraad installed and it works on our forms in preview mode. When we publish the form (this is a list form edited in InfoPath), it is not ...

That is an interesting question. The field by default is 'countryCode'. I just checked and it appears we may have changed the name. I hate it when that happens. Then we never know what the fields are............................ Thanks for your help!

I thought I fixed it. I did manage to get it to pull the 'physicalDeliverOfficeName' but not the Country Code. I got it to start displaying the properties that it is retrieving from the service. 'countryCode is not one of them. Is this by design or maybe that field is not promoted to where it can be accessed? As you can see, ...

I managed to fix it. Crazy as it sounds I moved the action to rule that runs after the strsubmitter is set by the first rule and it works.

Form is just a little too large to upload here

It does not appear to be retrieving any information at all. Not sure how it's getting the sAMAccountName. Please see attached screen shot. I have captured the set field value that is setting the sAMAccountName. The 2 other set value actions are exactly the same using their particular values of countryCode and ...

Having an odd issue using the getuserinfo method. I have a button that pulls employee info from the 'GetUserInfo' data connection of the Qdabraad webservice. I am successfully pulling the sAMAccountName and populating it into a text field. I am trying to pull these additional pieces of information and populate them into their ...

Actually I figured out how to do this with a multi-selection list box. It gives me exactly what I want and still gives me the clean look of the option button except with the square check box. I will post later on how I did it.

I am not sure that what I want to do can be done, but you are the guys who would know. I am reworking a form so that any variable that can possibly change in the future (list choices and such) are actually gathered from a data connection so the form does not have to be continually updated. One of my choices on the form is an option button ...

No, I wasn't referring to the 'Created Date' column. I was referring to fields in the InfoPath form itself that are formatted as date or date/time fields. When promoting your fields, you cannot 'allow users to edit data in this field by using a datasheet or properties page’ on any date formatted field. What this means is ...