SharePoint Designer Reviews

The previous version of the solution was good as we had different views of both the design and the code. The new version doesn't have the option to view data but it has other, better features though.

I would like to see some improvements when assigning a task. For instance, when you create a task or a subtask, there should be a better workflow. At this stage, we can't CC any names in the sent box. We can only use a "to" address. So when I want to send an email, I have to write a custom code through .NET and then send the mail. It takes up a lot of my time. Then I also found that there was a requirement from one of my customers that they want this option in the taskbar too. For instance, when the email gets sent, they want a CC option as well. 

I will rate this program a five out of ten. The reason for this is that I would like to be able to use SharePoint Designer without having to buy other third party programs. At this stage, I still have to use other designing webpages because SharePoint Designer doesn't offer all the features I need. You can create beautiful pages, add the list and add a document library, but the solution doesn't offer any complicated designing features. One can only do a few simple designs. Everything has to be coded through either Visual Studio or some other solution. So I hope to see an improvement in the new version of this program. Perhaps they can add different templates where one can add banners, tabs, and lists. And even drag and drop features where one can add permissions. That would be great. 

The most valuable feature is the capability of creating HTML pages, with CSS code. For example, most of the time I mirror in the web area, which means that I need to create an HTML file. Inside this HTML file I will write my web VBI.

Other valuable features are the ability able to update the master file, and creating the workflow.

Sometimes when I create my HTML page it is very slow and I don't know why. It's just stuck. I think that the performance needs to be enhanced.

If you compare the workflow with other engines like Olympus and K2, it is very complicated to create a workflow.

In the next release, I would like ready-made workflows that I can re-use and a way to apply a design for the master base that is less complicated.

This solution is stable.

I have not contacted technical support. With twelve years of experience, I can resolve the issues.

The deployment is used for both private and public clouds.

I would rate this solution a nine out of ten.

The solution's best feature is designing workflow processing. It's easy to change and collate workflows.

The solution has limitations when it comes to exploration.

The web services aspect of the solution is very weak.

If the requirements are moderate, the solution is okay, but for more complex requirements, I need to use the solution in combination with other solutions. It doesn't offer everything I need.

The stability is okay but limited.

The scalability is okay but limited.

The initial setup is straightforward.

We're using the SharePoint 2000 version.

The solution makes the work of estimating the requirements pretty difficult. Mainly, it is a very useful tool I can use for small to medium requirements.

If you're new to the solution, be aware that Sharepoint can be challenging, so you need to be ready to learn the solution in order to fully use it. Sharepoint involves coding; it's not like other solutions that offer zero coding. Organizations considering implementing it should be made aware of this.

If you are considering implementing it, I'd take the time to compare it to what you already have and any other options you are considering so that you are able to choose the solution that will work best for you. There are a lot of features now that are actually offered by competitors.

I'd rate the solution seven out of ten. If you were talking about the 2016 version, I'd give it a seven out of ten, but the 2013 version I would rate a six.

We primarily use the it as a creative solution for document management.

The document filing system is the solution's most valuable feature. We have used SharePoint as an option for a document managed system, like Documentum and IBM Filenet.

I believe Microsoft does not support Sharepoint on-premises. They only support Sharepoint on the Cloud. They should provide for both options and let the client choose their preference.

The solution should have a better workflow with the craft, and also offer some configurations to help drive workflow.

I'd rate the solution eight out of ten.

There are other solutions on the market. Some are more usable than Sharepoint.

The workflow is the solution's most valuable feature.

The solution is a bit complex. They should work to simplify it. 

The initial setup is complex.

We're using the 2013 version of the solution.

The solution has a lot of complexity. That might work for some people, depending on the use case, but for others, that may be a turn-off.

I would rate the solution seven out of ten. I'd rate it higher, but there are other solutions that are able to better cover my needs.

I use it mainly for workflows or for minor changes in SharePoint master pages.

I have setup many simple and complex workflows, very useful for daily automation (invoices, travel, leave approval) . It is also useful to make small branding customizations.

The most valuable aspects of the solution are the user-friendly interface and easy creation of workflow. 

Unfortunately Microsoft announced a few years ago that the last update for SharePoint Designer was released on August 2, 2016 and that Microsoft Flow will be the workflow designer and engine going forward.

I would add Nintex or all of the Nintex workflow to the solution if I could. I would add them to SharePoint Designer so that I would need to use only one workflow designer. Right now, I'm using SharePoint Designer and Nintex, and it would be better to centralize it.

The solution is stable.

SharePoint Designer is a very small tool, and very clever. You install it on your computer to access SharePoint's entire platform. In that sense, it's not a technology that's scalable or that needs to be scalable.

I've never had to contact technical support.

The initial setup is very easy. Deployment takes five minutes; it's basically just installing the software. 

I deployed the solution myself.

We use the on-premises deployment solution.

I'd rate the solution eight out of ten.

Our primary use case for SharePoint Designer is for implementation for clients.

What I like most about this solution, is that we can use it as a secondary customization platform. We do customization and make a web SharePoint live for our clients. 

From what I read online, it depends on what you use the program for. I think the customization and migration need to improve. Upgrading should be simpler without too many things you need to change or repair. 

SharePoint Designer should be more practical and become an extension of Visual Studio. Because Visual Studio is a universal development platform. So I don't want to have to switch my user ID every time. So it should be more flexible and more of a mobile app version and integration with other solutions.  

The program is perfectly stable. I really like Microsoft products because they are very advanced. I like SharePoint because it's big and the pricing is fair. 

The scalability of SharePoint is good and the program is fast. 

There is zero technical support. I have to use Google to fix the issues myself.

I used a smaller content management platform which I customized. Visual Studio and SharePoint Designer work well together and could be extensions to each other.

I struggle with the installation. We are not a small company and there are three equal sides. You need to get them right, otherwise, SharePoint won't install properly. A single installation takes a couple of hours. You need time to do separate functionality. 

The program wasn't easy to deploy either, because when I integrate solutions, I have to do so many things before I can deploy SharePoint. So the process is a little tedious due to the security features of the program, but once you get it, it becomes easier. But its always a challenge for someone who is unfamiliar with this program. 

I've never paid for SharePoint Designer. What I paid for is the SharePoint license, the cava, and then the client accesses the line fee. 

On a scale of one to ten, I rate this a five because it could be more flexible.

Our primary use is for file sharing on our intranet, as well as on the internet. We also develop internet applications.

The management and monitoring features are good.

The pricing is a little bit high and can be reduced. If we could pay for a single license that covers the whole organization then it would be better than paying fees based on the size of our user base.

We have been using SharePoint Designer for more than five years.

We haven't had any issues with technical support.

The cost of the license is based on the size of the user base.

In summary, this product allows our developers to do what they want to do.

I would rate this solution an eight out of ten.