SharePoint Designer [EOL] Reviews

We use the tool as a repository for the merger activities that occurred between two financial institutions. 

The tool offered us a seamless view of the documents that should be brought around to the executive management team members and other stakeholders. 

You can give document access to people based on their email addresses. You will also get notifications whenever the document is ready for review. 

I want the tool to be more approachable to people. I would like to see AI integration with the tool's future versions. 

I have been working with the solution for three years. 

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

The solution is scalable. 

The tool's initial deployment is complex. 

We have seen ROI with the use of the tool. 

The tool's pricing is cheap. 

I would rate the tool a four out of ten. You need to have an idea of how you are going to use the solution before implementing it. Once implemented, you can explore the tool. You can use ChatGPT for some advice. 

We create spreadsheets in Designer to collect data and integrate that with Power Apps and Power BI. We have about 50 or 60 users. 

Designer is easy to manage.

The user interface is sometimes not user-friendly.

I have been using SharePoint Designer for five years.

I rate SharePoint Designer nine out of 10 for stability. 

SharePoint Designer is scalable.

I rate Microsoft technical support nine out of 10. 

Positive

We used Excel.

SharePoint Designer is easy to set up. It's a cloud solution. We have about two or three people for deployment and maintenance. The deployment took one or two months. 

We deployed Designer in-house. 

We've seen a return.

I rate SharePoint Designer eight out of 10 for affordability.

I rate SharePoint Designer nine out of 10.

We are using it for the HR process. For example, we use it for personal leave, execution, and many things in HR. We create the forms and custom workflows and integrate them with Nintex workflows to automate the process. 

We also integrate this database with the Oracle 12C. It's a centralized database. After the flow or the workflow is done and approved, and there are many layers of approval, it'll go to Oracle. Basically, we integrate SharePoint with Oracle 12C.

SharePoint is great for content management of data. It makes our life easier.

Integrating SharePoint with other platforms is very useful. I can integrate SharePoint with Oracle and I can integrate Oracle with many databases. This makes our life here easier.

The initial setup was pretty easy.

The support on offer is helpful. 

The search capabilities need to be improved. They tried to make it better in the 2019 version, however, there's still more they can do. 

If the design code is in HTML, there is a bit of freezing that happens when opening in Sharepoint. 

I've been working with the solution for six years, and now I'm working as a programmer.

Just our developers use the solution. There are maybe 15 or so people using it at this time. 

Technical support has been excellent. They are always very helpful and responsive. We are satisfied with the level of support we get. 

I'm working on Nintex workflow and forms plus SharePoint. 

Also, I'm working in Azure, Power Apps, and Microsoft.

I found the initial setup to be very straightforward and simple. It's not overly complex or difficult. I deploy it every day for the end users. It's very easy.

We pay the licensing fees on a yearly basis. It's just a standard fee and there are no extras we need to add on or pay for. 

It's a very user-friendly solution. 

It makes programming and designing customization easier.

I'd rate the solution nine out of ten. 

Our use case for SharePoint Designer is customizing SharePoint.

What I found most valuable in SharePoint Designer is that through it, you can perform a lot of SharePoint functionalities, such as creating SharePoint lists and libraries, as well as customizing pages.

The pain point of SharePoint Designer is sometimes it gives you issues that can be resolved mostly by clearing the cache, but Microsoft should still work on it and make the product more stable.

Another issue related to SharePoint Designer is that with the newer SharePoint versions, Microsoft hasn't released a newer version of SharePoint Designer. Instead, Microsoft is recommending that you use the same old SharePoint Designer 2013. If Microsoft updates SharePoint Designer, the product will be more beneficial.

I've been using SharePoint Designer for ten or twelve years now.

SharePoint Designer is a stable product, and though sometimes it gives you issues, that can be resolved by clearing the cache.

SharePoint Designer has very good scalability.

We've never contacted technical support for SharePoint Designer. We just searched some online help forums where we get solutions to any product issues.

We haven't used a different solution for SharePoint. We've only been using SharePoint Designer.

The initial setup for SharePoint Designer requires no effort because it's a client application.

We implemented SharePoint Designer in-house. In the beginning, the vendor was involved, but after that, we did it in-house.

SharePoint Designer is a free product. It's SharePoint that needs a license, not SharePoint Designer.

Five people use SharePoint Designer within my company. Currently, there's no plan to increase the usage of the product.

One to two people take care of the deployment and maintenance of SharePoint Designer. Managers can use the product, but the technical staff uses it more.

Based on experience, I would recommend SharePoint Designer to other users because it's a product that's very easy to use, easy to set up, and provides a lot of functionalities in terms of customizing SharePoint.

My rating for SharePoint Designer is eight out of ten.

We are a consultancy and I am a project manager. We implement solutions for our customers and I have led several projects that involve SharePoint, as well as other similar technologies. My area of expertise is ECM, document management, information management, and related tasks.

The best business case for SharePoint is team collaboration. It can support a small team of people working on a project that involves an agenda, Wiki documents, and other related material. However, it's primarily used for temporary projects.

These days, I no longer work on SharePoint projects.

Using SharePoint helps our customers to better manage projects within their companies. Specifically, it allows them to easily connect people both internal and external to the organization and facilitates document exchange.

SharePoint has very good features for collaboration. 

One of the problems with SharePoint is that it claims to have so many features that people think they can do everything, and that is not correct. If you want to do everything, you're going to spend a lot of money to achieve your goals. Essentially, the marketing from Microsoft is very positive but from a consultancy point of view, it gets us in trouble because people have unrealistic expectations of the solution.

SharePoint is too complex to install and maintain.

The admin interface is poor, making it too complex to manage projects.

The integration with other products is poor. There are too many instances where we needed to call a third-party software company because functionality tried by the user in the other solution was not covered by SharePoint.

In the future, SharePoint needs to cover more of our needs for us to continue using it. For example, the workflow is not correctly integrated.

I have worked with SharePoint Designer for more than six years.

The stability of SharePoint depends on the client's architecture. If it's a simple installation then it's stable. But, in a more complex deployment, it is less reliable.

For example, I have worked with SharePoint in a highly complex organization in the financial industry. Every week, the system would crash. The IT would have to tell the users that it wasn't working and then resolve the issue.

Overall, it's not the best solution in terms of stability.

SharePoint is scalable, albeit complex.

We have approximately 10 customers that we have deployed SharePoint for. They have multidisciplinary teams, and people in many different roles use the software.

There are two levels of support for SharePoint. The first is from the company that sells it, which is the main integrator. The second level of support is from Microsoft, which is quite different.

Most of the time, the support from the integrator is valuable, whereas the support from Microsoft is too basic. I would rate the support from Microsoft a two out of five.

I have used several similar products including those from Alfresco, Laserfiche, and IBM.

The initial setup is highly complex and the deployment strategy varies depending on the needs of the client. It requires between one and three IT architects for the installation, depending on the customer's environment.

I would rate the ease of installation and setup a one out of five. 

In terms of ROI, I would rate SharePoint a one out of five.

Most of the time, our customer's license from Microsoft includes the cost of SharePoint. However, if you have to buy it then SharePoint is quite expensive.

I would rate the pricing a two out of five.

Based on my areas of expertise, I have to make recommendations to our clients about which solutions they should implement. I rarely advise my clients to use SharePoint. In fact, out of ten customers, on average, I would recommend SharePoint to two or three of them.

SharePoint is simply not dedicated enough to documentation management when people are looking for a real DMS or ECM solution.

My advice for anybody who is considering SharePoint is to first define your needs and then take quite a good look at the market. For tasks including document management, ECM, or a platform content service (PCS), most of the time, you will be better served by a solution other than SharePoint. If, on the other hand, you are looking for team collaboration, then SharePoint may be a good option.

Overall, I am not very satisfied with SharePoint.

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

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 SharePoint Designer to create SharePoint sites and applications for sharing information within our organization.

The Power App is the most valuable feature. We can design it to look exactly how we want it to be, without requiring an expert's assistance to set it up. We have the freedom to make changes on our own and can easily connect and generate leads.

Power Apps has certain limitations as it is designed primarily for tablets. When deployed on a computer, it becomes much smaller. I am currently facing the challenge of maximizing its functionality on a computer. This is one of the downsides of Power Apps.

SharePoint Designer needs filter options for lists and libraries. I want to create user groups and subgroups of users to apply properties to the metadata. Currently, I'm struggling to find a workaround.

I have been using SharePoint Designer for around three years.

SharePoint Designer seems to be stable.

I give SharePoint Designer a nine out of ten. We can create sites without having to code.

I recommend SharePoint Designer to others.