-
The only way I can imagine doing this would involve creating a database that is linked to Excel file -- which means an Access database -- and then creating a data connection to the Access database. Your Access DB would have to be someplace all form users could access it, with appropriate permissions. Here's a link to linking Excel with ...
-
Hi -- what is the full XPath of your expression? In the formula editor, click edit XPath, and you can paste it here. I have a feeling you need to be using current(). Also, is this IP 2003, 2007 or 2010?
-
So, it sounds like you can't publish ANY InfoPath forms to ANY of your SharePoint sites? I guess at this point I'd try to publish a form to a library from a different machine, or from your machine signed in as a different user, so you can start tracking down where the problem is. You may need to get your SharePoint admin involved -- ...
-
Is your form admin approved, a content type, or just published to a library? Your 2nd URL has the XSN location as FormServerTemplates/TEMPLATENAME.xsn. Your sample link above in your anchor tags has a URL as if the form was published to a library -- but with the template name instead of the correct "template.xsn".
If published to ...
-
In your original XPath, the XPath is absolute. So it is starting at the very top of the tree (if you look in the data source task pane) and finding the ItemDescription node... the first item description node. Your rule, however is firing based on the change of a ItemDescription node. That makes the ItemDescription node that is causing the rule to ...
-
MSDN says the Message property is availble for both client and browser.... So, I'd expect it to HAVE a Message property. What about the Site property? Does it also return null?
As a side note, there is an extra paren at the end of err.Message.ToString(), but I'm sure that's just a typo, 'cause you wouldn't be able to ...
-
Try this instead:
xdXDocument:GetDOM("OfficeSupplies")/dfs:myFields/dfs:dataFields/dfs:Office_Supplies/@BIN_NUMBER[../@ID = current()]
-
It sure looks from your description like you have this set up right.... Are you using InfoPath 2003 by any chance? Because if the filter isn't using current() to get the correct ItemDescription, that could be your problem, and as I recall, IP 2003 could be a bit flaky. Try this -- in the formula dialog, select edit XPath, and paste the results ...
-
Hi, and welcome!
You need to add a filter to the data values for your rules. Your rule is set on your main data source description field, right? And the rule sets the value of bin number (for example) to the bin number from the SharePoint list. But when you select that bin number from the SharePoint list data source, you need to add a filter to ...
-
Are you using InfoPath 2007? If so, you can right click on the field that is getting changed and use the logic inspector (rule inspector in IP 2010) to see what may be causing this field change. If you'd like, attach your template and let me know what field is changing, and I'm happy to take a look for you.