InfoPath Dev

You should be able to use the function userName() and compare that to all instances of accountid in the people picker field.  That should determine whether or not the current user is an approver or not. Hope this helps!

There are several techniques for how to do this such as web parts or InfoPath + qRules.  Here are a few tutorial videos that may help you out: http://www.youtube.com/watch?v=W6l27liMxX4 http://www.youtube.com/watch?v=85b7ftTJYo8&feature=youtu.be http://www.screencast.com/t/uV1u59TeMX

Hi there, I've attached a sample xsn which hopefully is the behaviour you are looking for.  Basically you need to use a formula as the default value of either a field or a calculated value.  Then use a filter to only count the values you want.  Let me know if you have any questions.

Hi there, Check out this tutorial video on cascading dropdowns: http://www.youtube.com/watch?v=SH7xUEcQwwg Hopefully that will answer some of the questions you have.  Otherwise, feel free to ask any specific questions you might have. Good luck!

There are a couple of ways you can go about this.  You can use a SP list connection then use query fields to only return the list item where the email matches the person who opened the form.  Then you can just use a rule to check what department that person belongs to. Or you can retrieve all the data and use rules again to filter ...

Hi there, Getting the form to print nicely can be sometimes tough in InfoPath.  The best suggestions I can really offer are 1) use read-only controls as much as possible (eg. calculated value, lists, etc.)  2) try using landscape to increase paper real estate  3) set up a separate print view that is specific only for ...

Hi there, I think what you are saying makes sense.  Unfortunately, InfoPath doesn't have a way to fire rules on the insert or remove action of a repeating table.  All of the rules in InfoPath are triggered off of either a button click or a field change.  Perhaps if you elaborated on your scenario a bit we can try to find a ...

The designer and filler are separate in 2010.  The designer is used for creating new forms and publishing it to SharePoint or some other location.  The filler is only used to fill out existing forms. This is why you see the different options in the File menu for both.

Sounds like you just want to select a value in a dropdown control (or something similar) then populate some details based on the value that was selected?  There are a few ways you can do this, but perhaps an easy way is using SharePoint list data connections.  If your lookup is in a SharePoint list you can use queryFields to do a search ...

That sounds annoying :( If its a client form, I'm afraid I don't have many suggestions for you on how to workaround the jumpiness.  Perhaps you can try to separate the sections into multiple views, so that there is only one section per view.  I'm thinking if you can reduce the content to a single page then you won't run ...