-
Adding the ID to each doc is far less of a hassle than having a bunch of folders that segregate your info and keep you from doing any sort of data manipulation across the board.
big question. Why do you have to have 4 separate documents? Why can't those other 3 docus just be built into the single InfoPath form as different ...
-
-
Depends on how you design it. If you have each question as a row within a layout table, then it will leave blanks. If you have a repeating table with conditional formatting to hide ones that don't apply, then it collapses. If you have them stacked on top of one another, then I think they will collapse. You have to play ...
-
Yes, 1 form with 1 view, multiple sections, and a field that states the phase (preferably a dropdown list with number values and text display names like 1 - Initiate, 2 - Execute, etc). You then put conditional formatting on each section to hide if the phase is not equal to 1...2...3...or whatever.
-
Yeah, folders are the old way of thinking and are like using shared folders, which are very limited. The new way is to use metadata. If you think about it, your folder name is nothing more than metadata that describes each document in a set. So, your unique ID that will be manually entered by the approver is the piece of metadata ...
-
Why do you want to "move" it and why do you want to use folders? Folders are not recommended if they can be avoided. It's best to use metadata and grouping/filtering within views to get the full use of MOSS 2007 content management abilities.
Is it possible that you explain your true goal as opposed to asking for specific ...
-
No, but there may be with 2010...just maybe!!! =P
Qdabra, the owner of this site, has their own solution that you might be able to leverage, but it wouldn't be for use with SharePoint if that's what you're doing.
You can do browser forms with managed code, but they require Full Trust and administrative approval.
-
I'm confused. I thought you said some other consultant wrote your AD web service, but you just said that you wrote it yourself? Reconcile that for me, please. Maybe you meant to say you wrote the workflow.
loginName is not a parameter that I've ever seen and is not what SharePoint uses to reference a ...
-
Ok, sharePoint doesn't use distribution lists. It only uses Security Groups, which many people mistake for distribution lists, because they behave like DLs (they can have email addresses and users). The "sync" with SharePoint groups is nothing more than adding an AD group to a SharePoint group. That way, the AD ...
-
Depends on what the workflow was built in. OOTB, SPD, VS?
It's apparently relevant to the loginName parameter that inveitably comes from the custom web service (such a shame when it's freely available otherwise). If you can't end up debugging the workflow, though I believe you can, you can try playing with that node from ...