Quote:
Originally Posted by arangas  I'd like to see: - content type for issues, risks, etc. defined at the site collection level (i.e. changing a list doesn't have to be done in EVERY workspace)
- reporting database allows reporting on any fields added/updated/removed from any workspace list
- lookup table that references a list of resource names
Out of your list the most important for me are workspace permissions, FBA, and backup/restore of config to XML.
Alex Angas Alex Angas | Good list.
#1 is interesting, more SP than PS... Along the same lines, I'd really like to see the capability of multisite template updates in the next version.
#2... this would be a tall order, but could be done... an interesting "bonus" would be the ability to add these custom fields into the cubes.
#3 is a good idea, but not one that I see Microsoft building in... However, you could accomplish the same thing using a timer job or event handler!
__________________ Stephen Sanderlin
Founder/Owner - EPMFAQ
Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post!
This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |