-
In my secondary data source, I have two pieces of information - the ID of the item and item name (which contains the prefix needed for the more complex XPath filter). In your secondary data source, I just see the ID. You should also include the info from your list that indicates the type.
-
Just to chime in - if you want to switch views on a field change, you have to use the context changed event. I like Ernesto's suggestion.
-
Do your users have read permissions to all lists or libraries your form is querying?
-
The forum is not always respectful of formatting - it can be rather fussy.
What you probably need to do is get a count of the cases with the same prefix - GEN, for example. I put together a simple sample form - save it locally, right click and select design and then preview to see the formula in action.
-
Check out this: http://support.microsoft.com/kb/892730
-
Did you check the blog post linked in my post above?
-
I would loop through this iterator:
XPathNodeIterator caseAttachments = this.MainDataSource.CreateNavigator().Select("/my:myFields/my:Details/my:Attachment", NamespaceManager);
And, actually, I'm guessing the repeating group is Details? So, I'd likely do something like this - get the repeating group
XPathNodeIterator ...
-
I think to query for just the items you need, you'll need code or a web service (like DBXL) to be able to get back items that are "like" what you are searching for (wildcard search) - I'm just thinking, my users are going to type in Henry and want to get back Henry Smith and Henry Jones, you know?
If you take that route, you ...
-
No - there is no way that qRules, which is executed from within the XSNs logic, can know that an XML has been deleted. You'd want to use some kind of custom workflow for this.
-
Perfect. So have you modified any of the items in the list after creating them? The XML sample has the last modified date/time and will compare it to the last modified date/time in the list to see what needs to be refreshed.