SharePoint Designer Reviews

We primarily use the solution as our internet and extranet platform and for our software.

The workflow is the solution's most valuable feature.

We work mostly with documentation and we'd like to have  it be more of a web-based. Right now, our product, our system is only set up for PDF and we're looking for a better web-based solution for our documentation.

The solution requires more web-based publishing. It would benefit from adding in more collaboration features as well.

The solution is stable.

The scalability is a little bit complex. We do have a lot of issues with scalability. It's not everything we hoped for.

We go through our own IT department, so we don't deal with technical support directly.

I'm not aware of our organization using a different solution. We've always used SharePoint Designer.

For our organization, it was quite complex. We have different departments in our group that require different access, which added a layer of complexity for us. The deployment took about a year.

We use the on-premises deployment model.

A lot of planning is necessary before deciding on a final solution or a final architecture. Planning is very important prior to implementation.

I'd rate the solution seven out of ten.

We were reviewing this tool for one of our clients — we work with both medium and large enterprises. Currently, they are using Documentum but they are interested in migrating to SharePoint, so they asked us to compare the two. I am part of an IT company where we do a lot of solutions and service-based IT. We do things for many customers from the IT side.

SharePoint Designer is for the developer or the administrator, it's not for the end product (the business user).

We use SharePoint to improve sequencing and workflow design in general, and it can be used to build a workflow process from end-to-end.

We also use the classic version of SharePoint to do work on the master page, pinning, and other things. We can use SharePoint Designer for that. We also copy our data from our SharePoint site by using SharePoint Designer to cut and paste.

SharePoint Designer is a great tool. The new workflow platform, Power Automate, which can be integrated with SharePoint Designer, is going to be great because currently, SharePoint Designer is only compatible with workflows.

Because things are moving toward the cloud, they should design a pin in SharePoint Designer that would be great because we do some coding for that.

SharePoint Designer should be integrated with SharePoint, for example, SharePoint Online can be integrated with SharePoint Designer to perform activities such as backup and restoration, that would provide a great advantage for developers and administrators. Naturally, this integration would also help Microsoft grow its SharePoint market.

We use Power Automate in the cloud, it would be great if we could do that with SharePoint Designer and publish it to the cloud. It would be nice if we could work offline, too. It is not always necessary to be online. The modern platform, from Microsoft Modern UI, is easily designed with integrated teams within SharePoint Designer, which will be a great advantage.

I have been using SharePoint since June 2007. We were using SharePoint Designer 2013, but we have recently upgraded to modern SharePoint; however, because the development platform was changed, the new SharePoint Designer is very limited, so we don't use SharePoint Designer very often.

Overall, it's quite stable, but sometimes it requires maintenance.

The scalability is not a problem because this is a desktop application and it works just fine. As long as your SharePoint site is scalable, the application will work just fine. 

The technical support from Microsoft is very good. We have never had any issues with them. 

From a user's perspective, it was simple. Microsoft is user-friendly and is always simple to use. 

The setup time is very quick. I don't remember exactly, but I would say it took maybe even less than five minutes. 

We do everything. Sometimes it requires maintenance and when it does, we do it.

SharePoint is included in your Office 365 package, you don't have to buy anything extra. There is no extra license required. Typically, many customers already have the Office 365 license in place so it's just a matter of leveraging Sharepoint Online.

SharePoint Designer is just a tool. As there are a lot of key factors, I would recommend using SharePoint Designer online for internal collaboration platforms. SharePoint is not only a document management system, but it also handles content management systems, workflow automation, process automation, and more. 

SharePoint Online is a product that is included in the Microsoft Office 365 package, it is not part of Microsoft Azure. Office 365 and Microsoft 365 is a separate product altogether. People do use SharePoint Designer within the SharePoint 2016 and 2019 on-premise versions, but I see a lot of customers moving to the cloud, so they use SharePoint Online. 

I would rate it a nine out of ten.

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.

The tool helps with document management. We use the solution to create workflows. 

SharePoint Designer doesn't support the features that are available in the latest version of SharePoint Online. 

I have been using the solution for around ten years. 

I would rate the solution's stability a nine out of ten. 

Microsoft's support is good. We haven't used support since we resolve the issues by ourselves. 

The solution's setup is easy and I would rate it a nine out of ten. The solution's deployment takes only a few minutes to complete. You need to log in with your credentials to connect with any of the SharePoint environments. It took only minimal resources to deploy the product. 

The tool is free of cost. 

I would rate the solution an eight out of ten. You can go ahead if you look to use 2010 or 2013 on-premises versions of the solution. However, it doesn't support the latest versions. 

We use this product to build applications for our systems such as project management and training.

We appreciate the fact that this solution can provide us with an on-premises version, as due to our geographical location, we are not able to use cloud-based tools.

We would like to see an improvement in the stability and overall consistency of performance in this solution.

We would also like to have more step by step instructions on build and customization, so that those without a programming background can easily use the tool.

We have been working with this solution for nearly three years.

This is a generally stable solution, although we do tend to experience issues when we configure the transaction load.

The initial setup of this version was very simple and straightforward.

 I recommend this product to any organization who wants to have a nice framework for building their apps.

I would rate this solution a seven 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.

We use this solution to access our cloud-based Microsoft applications.

We like that the interface is very user-friendly making it easy to use.

The solution is not very flexible when trying to access the solution via a personal PC.

We have been using this solution for two years.

We have found it to be a very stable product.

This solution is very scalable.

The setup for this solution is very straightforward as there is nothing to install; users can just log in and access the software.

The licensing for this solution is payable on a yearly basis.

I would rate this solution an eight out of ten.

Our main use case for this solution is to develop custom SharePoint sites. SharePoint is about collaboration to help improve efficiency, collaboration within teams, document management, and search. We have thousands of users in our client organization. We are a Microsoft gold partner.

SharePoint Designer has made information available centrally 24/7. It brings offline records online. It has made searching easy, without it document search was difficult. Communication between departments has become more effective.

I find the document management and search of SharePoint the most valuable features. 

I would like to see SharePoint improve the integration with different systems. I also would like to see more customization.

We have been using SharePoint Designer for 16 years.

SharePoint is stable.

Scalability has certain limitations depending on the number of users and number of records.

The availability and quality of technical support both need improvement.

Earlier, we used Custom.NET applications however, SharePoint is much better.

The initial setup is straightforward and gets simpler with every new version. The set-up takes less than a day, but the project for full implementation takes anywhere from 4 to 12 weeks. 

We used our own consultants to set up SharePoint. You need anywhere from 2 to 5 people and even upwards of 10 depending on the size of the portal to deploy and maintain SharePoint Designer.

Most of the SharePoint implementations are for the cloud which is priced per user per month. There are different plans at different costs that you can choose from.

We reviewed Custom.NET and other PHP based solutions prior to selecting SharePoint.

If you are implementing SharePoint Designer in your organization, I would recommend that you use the best practices given by Microsoft, specifically in implementation.

I would rate SharePoint an 8 out of 10.