SharePoint Designer [EOL] Reviews

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.

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.

We actually don't use Designer much in the latest version of SharePoint, since we can use any other designer in the new SharePoint architecture. Previously, however, we used SharePoint Designer 2013 widely for data mining, exploring the content, and editing. Those are the main features that you would need to use SharePoint Designer for.

SharePoint Designer is not releasing a new version. Version 2013 was the latest version. Now in 2019, we are still using the biggest version. It doesn't work properly anymore. Sometimes we experience issues, but there is no new version. 

There are many things that could be improved in SharePoint Designer. The user interface definitely is a very old design, but as a developer, I would concentrate more on the functionality. With the newer interfaces, just basic functionality is provided to explore the content. The editing method should be changed, as inline editing is not recommended. Now we create apps, which can change the user interface and the functionality as well.

There are some features that need to be worked out with the current version. There are several issues, but I can't think of them right now. There are lots of things that we to in newer versions. We use other tools for that, but that functionality was not possible with SharePoint Designer.

Some functionality is missing in the newer version, but in the previous version, it was good.

The initial setup was straightforward.

I've been working with SharePoint version 2013. I would rate it as 7.5 out of ten.

The basic functionality the solution makes it easy to share documents or information with the team. 

SharePoint is not a great product. It can be much better in many ways. 

The collaboration tools for editing do not work right and malfunction often.

It has a lot of bugs. It's also not very convenient. The UX/UI is not very user-friendly and not designed to be similar to other applications from Microsoft. 

The management functionality should be much easier. 

The dialogue with end users needs improvement. If you are a manager of SharePoint, sometimes it's hard to know what exactly the user would like to have. There should be more intelligent services or features available, which would make it easier for end users. 

There are many bugs in the solution, so I don't think it's extremely stable.

Although I'm not in charge of scaling the solution, I've heard it's not very easy to expand the capacity.

I've never contacted Microsoft directly, as our enterprise has its own internal support.

I didn't do the initial implementation, but I set up the team functionality, and that part of the setup was not easy.

We use the on-premises deployment model.

I'd rate the solution three out of ten.

My primary uses for this solution are attaching workflows and customizing pages.

Our deployment is mostly on-premises.

The most valuable feature is the capability to directly access the SharePoint data structure. It is a tool that is similar to a registry editor, but specific to SharePoint.

I would like to see the complete mapping of our data types, including previews, which were switched off at some point.

It would be helpful to have the SharePoint Designer capabilities built directly into SharePoint itself, into the management page, so as to create an online version of it directly in SharePoint.

There have been issues at times, but in general, it is stable.

This is a problem that does not occur at all. SharePoint Designer puts its configuration data into a firm structure, which is parallelized by default and thread protected. It does not matter which means you use in to access the data, whether it is through direct API calls or in SharePoint Designer. It is protected against all structures within the form. You cannot override data. It is inherently parallelized by SharePoint, itself.

There are approximately ten users working within our support company, but the company using this solution has about five hundred end-users.

I have contacted technical support in the past, and it took a few hours, but Microsoft called back and solved the problems. I found them to be pretty fast.

Prior to this solution, I was using PowerShell to perform the same tasks.

The initial setup of this solution is easy. There are just a few clicks, you enter the path and the licensing information, and then continue to click Next until it is finished. It is not like Oracle, where you have to know fifty parameters before installing.

This solution started as Microsoft FrontPage and was renamed at some time.

My advice for anybody who is implementing this tool is to make sure that you understand it. This tool can damage a lot if you don't know what you are doing. If you are only editing your own sites then there is not much damage you can do. However, if you have elevated access then you have to be careful. It is similar in this regard to a registry editor, where if you edit keys outside of your own personal scope then it can cause problems. You can do a lot of damage to your machine.

The biggest lesson that I learned when using this solution has to do with planning. When it comes to using this solution, it is much better to plan what you are doing in advance. Just clicking around trying to get things done is inefficient, and you will spend a lot more time than necessary.

I would rate this solution a nine out of ten.

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.

I use this solution for site development.

The most valuable feature is the development.

This solution could definitely be made easier to use.

This solution runs alright.

The technical support for this solution is fair. It's ok.

The initial setup of this solution is straightforward.

This solution is free of charge.

This product basically has all of the features that I need, but there is no such thing as a perfect solution.

I would rate this solution a seven out of ten.

The feature I find most valuable, is the workflow of the product. I have used it in the past to design different teller sellers, automating the business process using the workflows.

I think the product will soon not be supported anymore due to the new way of using those components in Microsoft flow and power apps. I have heard that Microsoft is not going to lease SharePoint Designer anymore.

I am not sure how stable the solution will be once Microsoft stops supporting it.

On a scale from one to ten, I rate this solution a seven. I like the user experience level and there were some small issues, but I can't remember what they were. It was a long time ago. If Microsoft will keep on supporting the program, they should fix those small issues.