What kind of risks are involved in running SharePoint designer solutions, such as embedding scripts in a web part (possibly an html web part)? I am a site administrator for a Team site, but I do not run the servers past that point.

Is there anything that I should avoid at all costs (like button that breaks everything)? I am also looking into running a combination of InfoPath and custom workflows. Will anything be an issue there as well? Thank you all.


Well, it depends. You should be able to work with workflows, lists, contenttypes, edit webparts on pages etc. without everything falling apart.

That said, there are minor flaws with using SharePoint Designer which has major impacts. When it comes to editing pages, SharePoint Designers HTML editor has tendencies to remove certain HTML tags when you save changes. I've also heard of and experienced some functionality to break in webparts because of case-sensitivity.

All I can say is avoid SharePoint Designer as much as possible and do most of your work through the SharePoint user interface. SharePoint Designer can be great for list management and such, but for pure editing, do that via SharePoint UI.

| improve this answer | |
  • OK, thank you so much. I am mainly worried about messing up other sites on the servers... not as much mine (because I could hopefully fix it); is there a chance of that as well? Basically I am planning to work through the ubiquitous Technet instruction on building a quiz with some of my own edits to customize where I store individual user results.(blogs.technet.com/b/brenclarke/archive/2009/04/14/…). – user2498810 Jun 26 '13 at 14:11

Having been using SharePoint designer to utilize some of the more advanced features (filter parameters, conditional formatting) I can say there are definitely situations where Designer can break your pages. I've never seen it break entire sites, or external SharePoint sites, but it has, from time to time, done some damage I consider to be unacceptable. I've not really been able to pin down 100% when/why these situations occur so there's always the risk it may alter your content in a way you don't desire.

From time to time I have used the Designer Advanced Editing mode to change the contents of aspx files. Usually I modify properties of web parts using the GUI. I've found this to be a little less clunky than the Browser interface (but much different) and there are also many features of SharePoint ONLY accessible this way. There are many inconsistencies between Designer and the Browswer interface. If you feel that some of these advanced configuration options that Designer allows are something you'd like to use, or need to use, than buckle down and enable versioning on all libraries containing pages you edit. That way, when something goes wrong you can roll back to the previous working version. You may find that trying to add a certain feature is akin to "banging one's head on the wall" but atleast you have that previous version to resort to when you just can't seem to make things work and Designer decides to eat your code.

I work in an organization where, among the server management group, there are large concerns that customizing Master Pages can break entire site collections. I'm not 100% sure where this fear comes from but I have heard that it stems from experiences with some previous versions that have now been patched (here at least.) These same site administrators also recommend that I not modify list/library entries with JavaScript. Again, not 100% sure why. I've done this successfully and find it to be quite helpful especially considering I don't have access to a Visual Studio license that would allow me to do the same stuff, better.

I've been using customized List Workflows created in SP Designer no problem. I've also successfully modified the new/view/edit forms using InfoPath and found this to be helpful as well. If you know InfoPath well enough you can create some forms that are actually user friendly (proper validation, conditionally filling form fields, etc) that the standard forms really don't offer.

One thing to note is that upon Publishing your latest workflow edit to the server in order to test functionality SharePoint creates a new version of the workflow. With List workflows the only way to delete previous versions is to go through the Browser interface. The ability to do seems to be absent from SP Designer. I found this out only after I got a somewhat disgruntled email from a sys. admin who asked me "Why do you have so many workflows?" I had no idea what he meant at first, and then he showed me.

Anyways. I could ramble more but I think I've illustrated my most critical experience with SharePoint designer.

| improve this answer | |
  • Thank you all so much! I've started looking at more OOB solutions because I really don't feel I am in the position to develop much in Designer. Thank you again!!! – user2498810 Jun 28 '13 at 19:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.