-
Hi Robert,
Printing is not an elegant area for InfoPath. In particular, paging - or, breaking the form into pages - is really not handled well. Matt Faus did an interesting blog on this a couple years ago but it requires code and some funky calculations when dealing with repeaters. To limit rich text fields, I would create a Print View that ...
-
Hi Mikko,
This is easy to do using the random number generator in C#. Too bad xpath doesn't support it. I've asked my team to add a Random rule to qRules v2.3 which we hope to release at the end of August. We're in beta test mode now. If you want to beta test qRules 2.3 (with the new rad Rand rule), just let us know. If you send ...
-
Hi Bo Nesbit,
Why not just use the out-of-box Email data cnnector? Tools->Data Connections->Add->E-mail->... ? That's a lot easier and you don't have to maintain code.
But, if you really want code, you can definitely do the same thing. There are lots of posts in this forum and information in the 2003 SDK (see InfoPath ...
-
Hi Ek38
When you created the data connection, did you specify that the field was primary key? You may want to look at the wizard again. I thought there was a specification required for single table cases. Usually, you'll have the repeating table under another table and that should work fine since it knows it's got a foreign key. This ...
-
Hi Niranjan,
First check that when you create a new form from 101 or 102 and try File->Save, does it default to the correct library? If so, you can get that value using code in an OnSave event handler. If not, read on...
With a content type, if you get the URL for the published template, it will indeed be the same for all form ...
-
Hi Pcheru,
This isn't a feature that InfoPath supports out-of-the-box. InfoPath can be used to add validation and to show a popup for example if the value isn't correct. That's easy to do.
Two other methods that you could do to get what you want:
Add an OnAfterChange event handler (code) to your form that checks the value and ...
-
Hi RogerGH and welcome!
Thanks for uploading your XSN. I took a look at it. I think the problem is your schema. field5 should not be repeating. Instead, add a group4 under group3 and then put field5 under that. Group4 should be marked as repeating. Then, add an OnChange rule to each of field1, field2, field3, and field4 that sets the ...
-
Hi Azhilenko,
This should work if the XML is changing. If you are changing the properties using another process, it may not work. Make sure the XML Modified Date is changing. If that is changing, you should look at your workflow in SPD. We've done this before so you should be good to go, but we would have to look at your workflow and formlib ...
-
Hi Catharine,
Are you using InfoPath 2007 or 2010? I saw this in InfoPath 2010 about 3 months ago and I thought it was a bug. At any rate, I think you can safely ignore it since the form should work fine. The Logic Inspector is just a read-only add-on. Somehow, it's failing to process the XSF. Probably a bug in the XSLT transform that ...
-
Hi Aravind,
This is a limitation of the out-of-box contact selector. You can use Qdabra's Contact Selector with Qdabra's Active Directory Web Service to do what you want. It will also work in the browser and be a more flexible option for you, but it's not free.
Another option would be to use Clayton Cobb's technique and ...