-
I'd forget the error to start with and ask, the area where the form is and where you're pull the data from, do you have access or more importantly who ever is filling out the form, do they?
-
If you don't want views, then I think you'll have to start having sections and hiding/showing as required. Personally 5 views is nothing.
As an aside my basic form has a minimum of 5 views before I've even started. It's based on various best practice comments/blogs etc. that I've read.
-
You could create a rule on the People Picker and AccountID
field. - Something like: http://www.sharepoint911.com/blogs/laura/Lists/Posts/Post.aspx?ID=178
-
All,
Potentially I have to use an InfoPath form to "look" into an SQL db. Assuming I can get my form to connect to the SQL db (never done it before).
As I understand it, the basic data will be a list of client names
The first problem is it's potentially to look at 40,000 client names. - This is somewhat of a non starter I think ...
-
Bisham,
I'll assume you're using InfoPath 2010 and SharePoint 2010. In addition that your form is in a web part page, thus you're filling out the form via a web browser.
Several things come to mind.
Create another list (InfoSec) and have a form load rule so that they have an InfoSec view which is only viewable by InfoSec ...
-
I think I understand what you're written
You would need a form approval status field. draft,submitted, approved, rejected or example.I assume this would be set on a button or something thereof.
Wait for form approval to equal submitted.
Then you'll need an else if if using Wait For X to equal today and/or if item is greater than today. ...
-
Jen
This is horrid when it happens. I use SP2010 and IP2010
We'll assume that the missing fields etc. are just hidden in a view on your SP library. - It happens. Also I think you should check your SP site and permissions.
I've seen people columns disappear/stop function when they are changed from a people ...
-
From my experience of dates and emailing. Make sure you email/network is solid. People come to rely on emails from workflows instead of looking at views in a SP library.
As every I turn to excel for this kind of stuff.
Youll need to create calculated colums within your library. The formula that seemed to work for me ...
-
Emailing of forms isn't something I do much of. That's my Friday sorted:)
Why not use the survery function in SharePoint or place the form inside of a web part page? Just send the users with an email and url in the body?
That way you could easily export the data to Excel and go Dashboard crazy or you can use the inbuilt chart ...
-
You could do something like:
Create a helper field i.e. PriorityHelp (put this on your form so that you know what follows works)
On your field Priority create a rule which says if Priority is blank set field value of PriorityHelp to value of Priority.
Test that the above works.
Then set the default value of the Priority field to ...