-
Sounds like a question for idautomation.com.
-
Good question. You could use the InfoPath Web Part in a branded page but then it's hard to pass the parameters when you navigate to it. I don't know if web parts have access to the query parameters passed to a page but if so, you could have the InfoPath web part load the form in question.
-
Hi Stara,
Is your email data connection configured to send the XSN as well as the XML? Maybe that's why you are seeing double, but it's just a guess.
-
Yes, but it requires calling SelectText which is code. Our qRules common library supports this via a rule - i.e. you don't need to write code. Otherwise, you'll have to add code to your form.
-
This should be documented in the SDK for InfoPath 2003. Go to resources on the right side of InfoPathDev. We should have a link for the SDK.
-
I have no idea.
You could install our Active Directory Web Service - it doesn't do this and it also fills a number of other gaps with GetProfilebyUsername.
Good luck,
-
Well, you can't, but you can connect fields to the webpart connections using the File->Form Options->Property Promotion dialog. Just make sure that your web part on your master page has parameters exposed to connect to it. Piece of cake in 2010.
-
Hi Corrie,
I wonder if this is related to another post: http://www.infopathdev.com/forums/p/21534/75411.aspx#75411
If so, it sounds like a bug that Microsoft fixed.
-
Hi JaxKookie,
I don't know why this is happening. The GUID you are seeing is generated on publish for a newly promoted property. If the name of the promoted property had some strange character in it, maybe that's why it is using the GUID. It should handle duplicate names fine, but that could be another reason I could imagine. It's ...
-
Hi Kerberos,
This is a very common request. You need to use current() and/or preceding-sibling functions in xpath to filter correctly for the current item. Search this forum for current() and you should fine related tposts.