InfoPath Dev

Hi Ghaith and welcome, You seem very close to a solution. Assuming you have a query that loads all of the data from this list (when the form opens or on some buttom click), you'll want to have two rules - one for supervisor and another for agent. If the supervisor opens the form (use a field with a condition) then your supervisor rule will ...

Hi DGajjar and welcome, We just webinar'd this last month (youtube.com/Qdabra) and showed a form that has automatic fixups. So, you can publish it anywhere and it will auto-fix up the data connections on load. See the "Change URLs view" in the attached sample an read the explanation at the bottom. Good luck!

Hi CMartinKo and welcome, You can map your forms to a list and use that to aggregate information on employees. To map form data to a list, you need to promote it to SharePoint form library (form options->promoted properties). Then, you create a workflow to add items to a list. We demonstrated this in our weekly webinar on June 27th. See the ...

Hello, Ok, I just found that my line breaks are not showing up, so this will be hard to read -- my apologies. I'm trying to pass info out of form's repeating table. Unfortunately, I cannot use QRules because of network security policies. My solution is to build a delimited string that essentially serves the purpose of a hash file. ...

Hi Helen, Why not remove the code and add qRules and use the Delete command? Benefits of qRules: common library for all forms data-driven, so when data source changes, code won't break reduces maintenance cost piece-of-cake easy cheap or free Free trial is here: http://www.qdabra.com/en/products/qRules_new.aspx. After you ...

Hi Pam and welcome, Thanks for working so hard to figure this out. If you have your People/Group pickers in a repeating table already, you could just use xsl:sort or qRules to sort the table in InfoPath. That will save you a bunch of time and you don't have to worry about promoting repeating values. To answer your question, though, you ...

Hi RoccoNH1, Switching to view before close won't cause the form to show that view on the next open (since that is a separate form instance). Just add a Status field and set that field instead. Then, add an Form Load rule (under the Data tab) that checks the value of that status field and switches to the view. Should be a piece of angel ...

Hi Michael and welcome, You could create a separate view and switch to that view when they open the form (add an on load rule) and that view can be parked as Read Only (ShP 2010/2013 feature) and that would prevent removal of the digisig and editing of the other fields.  

Here's a simple workaround: remove the email data connection from the InfoPath form and create a reusable SharePoint workflow on the form library that sends your email.  You may need to promote properties from your form in order to use them in the email fields. In addition, you cannot send the view, but you can send the link to the form, ...

Glad to hear it. Thanks for confirming.