SharePoint Designer Reviews

Within our organization, there are roughly 3,000 people, but very few of them interact with SharePoint Designer. We plan on using this solution in the future.

It stopped us from having to run around, manually exchanging documents. It's an online system, easy to access, and complete with document storage. Retrieving documents and uploading them is easy.

The user interface is good; it's easy to manage.

I have been using SharePoint Designer for approximately one year. 

SharePoint Designer is a very stable solution.

We have our own IT team that handles most maintenance related problems. When we have interacted with customer support, they have always helped us.

Before SharePoint Designer was introduced, we used to have a manual documentation system — we had to run from one corner of the building to the other, looking for someone. SharePoint has made things a lot easier.

We did a revamp. We migrated from another version. A team then showed us how to operate it properly and made sure we were very comfortable navigating it. It's very easy to use.

I would highly recommend this solution. 

On a scale from one to ten, I would give SharePoint Designer a rating of nine. If they included some training modules, I would give them a ten, because that would make it even more user-friendly.

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 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.

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.

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 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 are using SharePoint Designer for sharing knowledge.

SharePoint Designer could improve by making the searching feature better. It is not accurate in some cases, and there are some descriptions that are not clear.

I have been using SharePoint Designer for approximately five years.

There are some bugs in the solution but it works. There are problems with the server.

The solution is scalable.

We are a small company with five people using the solution. If we grow it will be approximately 10 to 15.

If we ever have a problem we contact our consulting company for assistance.

I did not evaluate other solutions prior to SharePoint Designer.

The initial setup of SharePoint Designer was simple. It took approximately one week.

We used a consultant company for the deployment and with our processes.

I use Macintosh devices, and because this solution is not available in the Apple Ecosystem I use it because it is cost-effective.

We achieved the discount rate for the solution and the price is low for this year, but I think it will increase next year. It cost approximately €10 per user with a discount.

We do not need anyone to maintain the solution, we contact our consultant company if we need to.

My advice to others is to use a good consulting company to assist them with the implementation of the solution.

I rate SharePoint Designer an eight out of ten.