-
So, I'm not sure I understand exactly what you are saying - is the file attachment still present after you've saved the file to SharePoint? That would explain base64Binary in the XML....
-
You must mean for an IP 2007 browser form?
If so, I'd suggest you try qRules - there is a command that can be used to add a filter to an owssvr.dll connection to return filtered data. Otherwise - you'll need web services (to return your data pre-filtered) or custom code, I'm afraid.
-
It isn't an error - just an informational message. InfoPath just wants you to know you have the same control on the form more than once.
-
I should have been more clear - does your code work when you preview your form from designer? If not, you can run in debug to figure out what is wrong.
EDIT: Also, you can post your code if you'd like - someone may be able to see what it going wrong.
-
Well - InfoPath doesn't really have a show if - you can add conditional formatting to your section that says "if this field is NOT equal to this value, hide this section".
So, let's say you want the section to show if your field has a value of "Approved". The conditional formatting would be set to hide the control if ...
-
Thanks, Karsten, for adding that - I should have mentioned it specifically. It can be kind of confusing, especially for those not accustomed to reading MSDN documentation.
-
Okay - so that tells us the issue is with the environment - anything in the log at that time?
-
So, let me try again to explain what I'd like you to do, because I feel like I am failing to describe it.
What is the name of your data connection that uses the owssvr.dll data connection?
Is it FilterOwssvr?
Drag the repeating data fields from that data source from the data source task pane onto the form (sounds like you've already ...
-
So, this is helpful - looks like that data connection is failing when you are using certain user IDs (standard user).
Anything in the log from InfoPath Forms Services when you open the form as a standard user (I'm assuming that you still have the data connection set to run on load, and that is why you are getting data when you ...
-
Where ever you have the rule that runs the command, follow that rule with a rule action that sets your field to the value of the result field... make sense?