Would you like to help shape the future of how Microsoft Office SharePoint Designer works with data inside your SharePoint application? And be entered in a sweepstakes to win 1 of 5 FREE copies of Microsoft Office 2007 Professional? If yes, read on.
To help inform SharePoint Designer plans and designs in this area, we’re asking key customers to complete a short survey about your needs for data and view design, features, and functionality.
Everyone who completes the entire survey (and opts to be included in the sweepstakes raffle) will be entered in a sweepstakes for 1 of 5 FREE copies of Microsoft Office 2007 Professional. The survey is about 40 questions long, mostly multiple choice, and takes an average of ~15 minutes to complete. (Because of branching logic, the number of questions you see, and time to complete the survey, varies depending on your answers to specific questions.)
If you’re interested in helping us out and shaping the future of Microsoft Office SharePoint Designer, please take this link to access the survey.
The survey will remain open for responses until September 24, 2007.
Thank you!The SPD User Experience Team
More information about SharePoint Designer is available here.More information about Microsoft User Experience is available here.
If you have questions about this survey, please email us at firstname.lastname@example.org. Reference the "SharePoint Designer Data Team Survey."
no matter what I enter in today's date .. it always says you must acknowledge ... blah blah
atleast the required format of date should be specified ...
Quick Links Security - Platforms - Internet – SQL Server - Unified Comms - Manageability The TRM blog...
i missed the survey. so i thought i leave a comment here and hope this gets to the team.
Can we have SPD as the only tool for SharePoint development. Now what i mean is, In SPD when i click on File --New i should get WebParts , Features, also apart from the rest of the things on the New dialog box. Thus i would not have to leave SPD if i have to write a custom webpart, and go to Visual Studio (VS) to write a webpart.
Similarly for features. This would then make the SPD a complete SharePoint development environment. I would not need VS.
If i want to be a SharePoint developer only then i do not need any thing and i don't need to do hop skip and jump.
I hope this is conveyed to the SPD tool team.t
This information comes from the Technical Rollup Mail blog which can be found here http://blogs.technet
Well i was too late getting to the survey so I'll provide some feedback here.
Things I have to have.
1. Be able to open multiple workflow designer windows.
2. Be able to cut/paste code within and between workflow designer windows.
3. Be able to cut/paste substitution fields for building dynamic strings or emails
4. Be able to select multiple substitution fields when adding to an email or building dynamic strings.
5. Be able to easily package a workflow and migrate it to another SharePoint environment, and run a process on it to associate it with a list. It should attempt to remap underlying elements but also provide me with an interface to do this manually.
6. Be able to provide inline comments in a workflow so I don't have to document the logic externally.
7. Prevent an onchange workflow from instantiating when I modify an item in an onchange workflow for the same list.