-
Yes, there is a way to do this.In a rule before your SaveToSharePoint rule, execute the GetAttachmentAttribute command with /attr=name. This will return the name of the attachment to the Qdabra Rules result node.In your SaveToSharePoint rule, you'll need to use a formula instead of just setting the value to a string in your rule to set the ...
-
I *heart* this post so much.
So, a little more info, please - what are you doing when you get this message? Trying to open the XSN (the form template itself) in design mode?
-
Does it return data in the browser? Is the error occurring when the data connection executes?
When you open in filler, the user profile web service is going to work w/ your user name from Windows - jsmith, whatever. But then, in the browser, it wants your claims user name.... And that isn't what's being passed to the data ...
-
Is your data connection executing on load? I would set it to not do that. I'd drag the query field onto the form and add a button that executes the query. I'd put some data fields on the form too so I'd know if I got anything back. Then add a calculated value on the form with the userName() function as the value. Publish, and open in ...
-
http://www.infopathdev.com/blogs/hilary/archive/2009/06/07/hack-manifest-xsf-to-filter-the-target-of-a-rule.aspx may help - it describes manually modifying the manifest file of the template to add XPath filters to the target for a rule.
-
Can you use rules for this instead of code? Just add a Form Load rule to update the status field. If you must use code for some reason, this should get you started: http://msdn.microsoft.com/en-us/library/office/aa945227.aspx
-
The first thing I check on this is postback - your rule is on a button or a field - make sure either the button or the control bound to the field has postback set to always (under the control properties / browser tab).
-
Can you just hide the control if it is blank in your updated form? Will that work? You can also get the form's version via an expression like this:
substring-before(substring-after(/processing-instruction()[local-name(.) = "mso-infoPathSolution"], 'solutionVersion="'), '"')
Perhaps hide the control ...
-
So - are the users submitting the form to your SharePoint library using your data connection? Or are they saving the form there, and just using Form1 as the name? You can always disable Save & Save As, force them to only use Submit, which should then submit to the form library.
However, if you are using "now" for the file name in ...
-
This is true. If you try to open the existing XML with the form after moving the fields, you will lose data.
Unfortunately, there is no simple way to approach this. You could:Branch the form - clean it up, create a new library that uses the new form and leave the old form with the old libraryBranch the form and instead of using a new ...