Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Use of Sharepoint Designer in production environment

  Asked By: Ojas    Date: Dec 27    Category: Sharepoint    Views: 3139

We are not allowed to use Sharepoint Designer on our production environment. We
can use it for prototyping on the development lan, but we can't move anything we
create across to the production lan. We can only write code on our development
LAN to use to create features to install on the production LAN. Is there a good
written justification out there to help us persuade the powers that be that we
should be allowed to use Sharepoint Designer on the production lan?



3 Answers Found

Answer #1    Answered By: Xiomara Blanchard     Answered On: Dec 27

This isn't what you're going to want to hear, but I think the policy of not
using SPD in production  is a good one and I wish I could get it implemented
at my organization!

I find it very difficult to migrate and deploy SPD customized items,
ESPECIALLY SPD workflows. As you probably know, SPD workflows aren't easily
(if at all) moveable between lists. I have users who create  complex SPD
workflows and then ask me to move  them onto a different site and they don't
realize that they cannot be moved.

If you a code  a feature, everything can be self contained in the package and
they are just much easier to handle from an administrative standpoint.

Answer #2    Answered By: Rosemarie Cervantes     Answered On: Dec 27

I'm sorry, but I disagree with that conclusion. Yes, it is difficult to
migrate things customized using SPD, but that's exactly why SPD MUST be used
in a production  environment and not just in a development  sandbox. I agree
that SPD workflows can't be moved. But that doesn't mean you shouldn't
build them in production. It just means that you should build them where
they need to be. If your users are asking you to move  them to a different
site after creating them then the problem isn't SPD workflows. The problem
is that users haven't been trained or informed about how to use them

One of the major design goals for SharePoint was to get ownership and
control of information out of the IT department and into the hands of the
people whose data it actually is. SPD is a major tool in fulfilling that
goal. I'm a developer and I really LIKE features  and solutions. But
limiting everything to being created in a separate environment  and then
deployed as a feature in a solution defeats the whole purpose for having

Yes, limiting usage of SPD in your production environment will make the life
of the IT staff easier. But whoever said making life easier for IT was the
reason to use SharePoint? Companies install  SharePoint to provide users
with a better set of tools for managing the information that is the
lifeblood of any company in the modern age.

I'll get down from my soapbox now and go away quietly....

In answer to the original question: I wish I could provide you with a
document that would support you. But the reality is that the company
decision makers either understand what SPD is for, or they don't. If they
think things can be developed separately using SPD and then migrated to the
production environment then they don't understand how SPD works.

Answer #3    Answered By: Manan Kadu     Answered On: Dec 27

I do, and I don't understand organizations that ban the use of SPD. Fear is the
motivating factor for this, in my opinion. Fear of something they simply do not
understand and so, ban its use. Designer can be a very powerful tool to allow
users to customize aspects of their sites in a SharePoint environment. The issue
is, as Paul points out, they simply don't understand how it works. Like any
other powerful tool, some training must be provided before allowing someone to
use the tool. Organizations don't want to have to do this, so they simply say;
This is bad, you can't have it.

Designer is designed as a site based customization tool. It is not meant for
Enterprise modifications and if you try and use for such things you will only
frustrate yourself. However, don't blame Microsoft because you were trying to
pull out a splinter with a pair of pliers.

Didn't find what you were looking for? Find more on Use of Sharepoint Designer in production environment Or get search suggestion and latest updates.