-
Unless you are looking to add the same, static plain text, not really. If you were, you could add the text as a default value to a node (or a secondary data source) and use a calculated value to display the text. Then you could just change the default to update all the views.
-
Challenge accepted (though I just used dropdown boxes for Risk & Probability due to being lazy). Download the attached sample, right click, select Design & from there you can preview. The matrix.xml is a resource file in the form, so you can see how I set it up. :)
-
So - this is a report that is using a SharePoint List for the data source, and I think you are saying that you have the possible options separated out for selection as a parameter, but the data returned isn't correct? If I recall correctly, with a report using a list for a data source, user passed in params don't work & you have ...
-
Unfortunately, unless you are using a list form, it is pretty hard to submit InfoPath data to a list. The company I work for makes a product that simplifies this - you can download a free trial here. Otherwise, you have to write custom code, or use CAML to submit (you can find a couple mega posts on this forum outlining using CAML and web ...
-
Sorry I was so slow to reply to this! I think I'd use an XML file as a resource in the form for this - let me know if you are still considering options and I can work up a sample for you.
-
Unfortunately, your picture doesn't show. But, so you know, signing the form adds nodes to the form - so you can't actually just add a rule to your signature group. If you take a look at one of your signed XML files in a text editor like Notepad++ you'll see a "Signature" node added to each of the signature groups (or ...
-
With custom validation rules, sometimes you don't want them to fire if the field is just blank - instead you are looking for it to contain specific values. Validation goes on specific fields - although if you prefer, you can add rules on submit to simply block submittal if specific fields are blank or don't have the correct values.
-
That is always a bit of a mess. I'd guess that the form isn't currently in use, since you hadn't been able to get it published as a browser form? If so - I'd probably remove the content type and all of the columns, then publish it up again.
-
Are there any errors when you open the form? I would probably drag the secondary data source that provides the dropdown values onto the form (temporarily) so that I could see if data was being returned, in order to try to narrow this down. Maybe add a button that queries the data source to see what happens if you query it after the form ...
-
Whooo hooo! glad that worked. :)