InfoPath Dev

I'm creating a custom sharepoint 2013 list form, and trying to apply some simple styling to a people picker field i.e. I'm trying to shade all of my input fields the same color. All of my input fields including the people picker look great in InfoPath / preview, but when I publish the form to the SharePoint ...

 I was able to pull this off, but you have to think backwards. Basically when your doing an is XXXX = YYYY in a data filter, if you want to apply a function, you can only do it in the YYYY part.. so instead of doing is TRANSLATE(XXX, "ABC", "abc") = YYY I had to switch it to, is YYY = TRANSLATE(XXX, "ABC" , ...

This was a secondary data source. I ended up using a translate in the form so that it was able to normalize the data and do the comparison. I'd still love to know if T-SQL is possible, I couldn't find anything in the DOCS. it doesn't seem like it works at all though.    

I'm trying to do something similar, but not sure how this solution applies to my context. I am returning data from an SQL query, and attempting to use a filter to return the data from the SQL query only when one of the columns matches the accountID of a person field @COLUMNA[COLUMNB = AccountID] in my form My problem is in the SQL ...

I have a successful data connection, and in the udcx file, I have a SQL query that is successful, however i would like to use a T-SQL function LOWER() to return one particular column back in all lower case. When I try to do this, the column does not return any data. After some googling I have come up with zero leads on if it's even possible ...

I was able to get it to work by changing all the fields and using the Set inner XML action with the Xpath code to the particular field.

Hello, I've been searching for an answer to this, but I am having trouble finding one already posted. Here is my question. I have a custom workflow that sends an email to a user based on the value of a people picker in the form. We have situations that require that name to be changed from the original person to a new person. ...

Thank you so much, I didn't know that I could set a rule to just run like that! Thank you!

I have a form that users can fill out by either typing in by hand, or by using a barcode scanner attached to a computer. Unfortunately the bar-code contains an extra character we do not want. If a user scans our part number field, the scanner inputs "PXXXXXXXXX" If the user types in the number by hand they simply omit that P. ...

I think there would need to be another submit button on the form though, the person filling out the form for the first time needs to submit it. It's then sent to the approver(s) and they will need to approve/reject. I would probably disable the submit button once the form has been submitted to the approver(s)