Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Good Experience using Dell Boomi
What do you like best about the product?
Good On Time Support. Lots of Good Features and excellent light weight capabilities
What do you dislike about the product?
Does not support Transactions. Need more workshops focusing on Architecture and helping Administrators understand how to build up environment based on requirements.
What problems is the product solving and how is that benefiting you?
Faster Integrations.
Low Learning curves.
Ease in Implementing
Low Learning curves.
Ease in Implementing
- Leave a Comment |
- Mark review as helpful
Boomi is powerful and highly usable, but not perfect
What do you like best about the product?
Dell Boomi's interface is mostly intuitive and it makes basic ETL integrations easy to build and deploy. As I've used it more and more over the past few years, for more complex use cases, I've learned that it sometimes has unsurprising (and not so obvious) depth, though this depth is often not as well documented as it could be.
What do you dislike about the product?
There are a few things that Boomi struggles with:
- Mapping values between two dynamic JSON arrays is a true challenge. If you need to map array elements from Array 1 into Y array elements in Array 2...well, have fun setting that up. Easy to do in code, but quite unintuitive and nearly impossible to do in Boomi. I was able to get a demonstration from a Boomi customer service rep and the solution provided was not scalable.
- Basic UX details can be rough at times (and the interface itself takes up too much screen space)
- Stuck on an ancient version of Groovy for embedded code
- No built-in code IDE even though you'll need to embed more and more code as you increase the complexity and sophistication of your integrations.
- Mapping values between two dynamic JSON arrays is a true challenge. If you need to map array elements from Array 1 into Y array elements in Array 2...well, have fun setting that up. Easy to do in code, but quite unintuitive and nearly impossible to do in Boomi. I was able to get a demonstration from a Boomi customer service rep and the solution provided was not scalable.
- Basic UX details can be rough at times (and the interface itself takes up too much screen space)
- Stuck on an ancient version of Groovy for embedded code
- No built-in code IDE even though you'll need to embed more and more code as you increase the complexity and sophistication of your integrations.
What problems is the product solving and how is that benefiting you?
We're solving a variety of business problems, but primarily automating manual processes that involve typical ETL operations. We've managed to save many hours of manual work and the accompanying potential for human error by using Dell Boomi.
Awesome
What do you like best about the product?
# A universal connect-up and integration tool with almost all known sources.
# Easy to understand interface
# Detailed and informative logs
# Frequent updates to ensure new features, bug fixing and stability
# Quick customer support
# Easy to understand interface
# Detailed and informative logs
# Frequent updates to ensure new features, bug fixing and stability
# Quick customer support
What do you dislike about the product?
# Several features populate very slow. For instance, the left menu, drop-downs. It could be saved on sessions and can be provided at an instant. If any change is required, option for refresh could be given as separate rather than compulsory update.
# Choice to download deployed process lists. Time filters on deployed processes.
# Garbage collection doesn't seems profound
# Choice to download deployed process lists. Time filters on deployed processes.
# Garbage collection doesn't seems profound
What problems is the product solving and how is that benefiting you?
I face numerous EDI integrations for our clients.
It also includes majorly AS2 processes, TPs, SFTP, Disk, FTP.
Easy integrations on various profile types
Easy connector and trading partner configurations
It also includes majorly AS2 processes, TPs, SFTP, Disk, FTP.
Easy integrations on various profile types
Easy connector and trading partner configurations
Worked as a B2B Integration Specialist on the Boomi and Boomi Atomsphere platform for past six years
What do you like best about the product?
Flexibility and versatility of integration options.
What do you dislike about the product?
Licensing of the product by Trading Partners and connections is limiting and can be expensive.
What problems is the product solving and how is that benefiting you?
B2B/EDI/XML/CSV/MSSQL and cloud integrations over SFTP, FTP, AS2 communications.
Recommendations to others considering the product:
Good B2B/EDI solution for a small to mid-size company with integration needs.
The licensing of the product does not lend itself to a large number of trading partner and connection needs.
Would be a much more scalable product if was licensed by adapter type and perhaps a sliding scale of trading partners deployed, instead of by every trading partner and connection.
The licensing of the product does not lend itself to a large number of trading partner and connection needs.
Would be a much more scalable product if was licensed by adapter type and perhaps a sliding scale of trading partners deployed, instead of by every trading partner and connection.
Flexible & Powerful / API, UX Issues
What do you like best about the product?
Boomi is a flexible and powerful solution for data integration. It has shown itself to be very stable once the processes have been created. There's a lot of versatility under the hood, it just sometimes takes a lot of work to figure out the right/best way to implement a given process. It was a more cost-effective option compared to some other solutions we examined.
What do you dislike about the product?
I found the Boomi learning curve to be quite steep and the documentation (specifically examples of working processes) to be lacking. Basic integrations are straightforward, but complex processes require a lot of moving parts, some of them buried behind multiple layers of windows. As a developer, it is frustrating to spend 20 clicks on doing something that could be written in a couple lines of code. I was longing for a full-featured API to set up the processes and mapping in some sort of domain-specific language, but alas, none exists. I also feel like the UI could use some improvement. The process/connector browser, specifically, gets quite cumbersome when working with multiple projects and/or complex integrations. Having to manually switch over all the connectors over when moving to production seems overly painful. I'm constantly worried that something will be missed in a deep layer that will cause the integration to fail. Again, I'm just used to working with code and Boomi feels like coding via UI.
What problems is the product solving and how is that benefiting you?
Two-way data integration with Salesforce and an external database. Other one-way integrations to support various systems.
Recommendations to others considering the product:
Does what it advertises, but there may be other competitors that are worth a look.
Quick and powerful 1-stop shop for integration
What do you like best about the product?
Very intuitive environment, the web interface can be used immediately from anyone familiar with the basic of application integration. The learning curve is really fast. A single web-based environments supports all the phases from design, to deployment and management.
If you need to do scripting you can use industry standard languages like Javascript and Groovy.
The need of custom scripting is limited.
The central control from the web console of all the managed processes is a giant leap in terms of DevOps respect to more traditional products.
If you need to do scripting you can use industry standard languages like Javascript and Groovy.
The need of custom scripting is limited.
The central control from the web console of all the managed processes is a giant leap in terms of DevOps respect to more traditional products.
What do you dislike about the product?
The pricing and sizing require usually strong analysis with the customer during the presales phase. Some customers are not willing to engage into this and might lead to difficulties in attaining a competitive sizing for the projects.
What problems is the product solving and how is that benefiting you?
This is an integration product, the key objectives usually are:
- perform scheduled ETL processes
- expose and consume WebServices within a SOA architecture (ESB type)
- fast implementation: this is usually the only key benefit most customers care for
- perform scheduled ETL processes
- expose and consume WebServices within a SOA architecture (ESB type)
- fast implementation: this is usually the only key benefit most customers care for
Recommendations to others considering the product:
Before evaluating an iPaaS product consider if you can accept a command and control architecture which is being governed from the US laws. Most state-owned companies from EU will not like that.
Don't be afraid of the pricing: a careful architecture design and discussion with the vendor/partner will ensure you get real value for money.
Don't be afraid of the pricing: a careful architecture design and discussion with the vendor/partner will ensure you get real value for money.
Dell Boomi Review
What do you like best about the product?
Integration with cloud applications like salesforce.
What do you dislike about the product?
It's not matured enough to integrate with ERP applications like SAP. We need to depend on work around solutions that makes difficult to integrate with SAP
What problems is the product solving and how is that benefiting you?
Easy integration with Salesforce.
Recommendations to others considering the product:
Needs to built strong adapters like RFC Listener and also improvements needs to be done in the existing IDoc connectors.
We need to have strong mapping builder. The current mapping builder is not strong compared other middleware tools.
We need to have strong mapping builder. The current mapping builder is not strong compared other middleware tools.
A great iPaaS with enormous potential
What do you like best about the product?
There are many good things about Dell Boomi that I have come to like and use in everyday work, the overall capabilities together with continuous improvements from the R&D team creates a product that you feel is not satisfying itself with its current status but always trying to adhere to customer needs and suggestion. To mention a few of the parts I like the most I would point out the following:
Environment management between Test and Production, or whatever other steps in between, is made very easy through Boomi and this makes the overall development and maintenance a pure delight once you have this setup to cover your needs.
The Scripting functionalities, both inside a process and inside a Map function, give you a very extensive set of new ways to solve a complex business case for a Customer. Covering both JavaScript and Groovy this is a very powerful addition which makes the development easy even in tough use cases.
API management and the overall capabilities for creating and maintaining Web Services, it is very easy to setup and utilize as part of your integration.
Last but not least, Boomi is doing more and more updates to increase the usability and the user experience which I find very interesting and good. There is almost always some improvements regarding UI etc. in new releases and they manage to do this without making it difficult for us, the users, to keep up and adapting to the new look and feel.
Environment management between Test and Production, or whatever other steps in between, is made very easy through Boomi and this makes the overall development and maintenance a pure delight once you have this setup to cover your needs.
The Scripting functionalities, both inside a process and inside a Map function, give you a very extensive set of new ways to solve a complex business case for a Customer. Covering both JavaScript and Groovy this is a very powerful addition which makes the development easy even in tough use cases.
API management and the overall capabilities for creating and maintaining Web Services, it is very easy to setup and utilize as part of your integration.
Last but not least, Boomi is doing more and more updates to increase the usability and the user experience which I find very interesting and good. There is almost always some improvements regarding UI etc. in new releases and they manage to do this without making it difficult for us, the users, to keep up and adapting to the new look and feel.
What do you dislike about the product?
There are small areas where I really hope that they make some improvements:
When it comes to custom scripting utilizing JavaScript or Groovy it would be very good to have syntax highlighting or similar regular features to simplify the development and minimize the risk of syntax issues.
The very good SOAP Connector, which is used for all connections using the SOAP framework, does not support NTLM/Kerberos authentication, which leaves you with the only option (if your use case cannot use oData) to develop a branded connector.
Overall the documentation is ok, and their new Community is very good, but I would like some more concrete examples in their regular documentation. Very often I read documentation about a Connector or some other shape and the bare minimal is available; sometimes a checkbox is explained by re-typing its label, which is quite annoying if you are looking for a deeper explanation of the impact of actually checking this checkbox.
When it comes to custom scripting utilizing JavaScript or Groovy it would be very good to have syntax highlighting or similar regular features to simplify the development and minimize the risk of syntax issues.
The very good SOAP Connector, which is used for all connections using the SOAP framework, does not support NTLM/Kerberos authentication, which leaves you with the only option (if your use case cannot use oData) to develop a branded connector.
Overall the documentation is ok, and their new Community is very good, but I would like some more concrete examples in their regular documentation. Very often I read documentation about a Connector or some other shape and the bare minimal is available; sometimes a checkbox is explained by re-typing its label, which is quite annoying if you are looking for a deeper explanation of the impact of actually checking this checkbox.
What problems is the product solving and how is that benefiting you?
Integration to multiple systems including Salesforce, Microsoft Dynamics Navision and third party vendors.
Developing and maintaining API and web services is a key aspect that is necessary for our implementation, this together with integration towards Salesforce for not only custom built web services but also standard operations such as Querying, Insert/Upsert/Update/Merge/Delete is vital for the success to be achieved.
Ability to streamline the integration and having a cloud based solution
Developing and maintaining API and web services is a key aspect that is necessary for our implementation, this together with integration towards Salesforce for not only custom built web services but also standard operations such as Querying, Insert/Upsert/Update/Merge/Delete is vital for the success to be achieved.
Ability to streamline the integration and having a cloud based solution
Recommendations to others considering the product:
Read up on licensing and how you best maintain and handle your connections in regard to the contract that you sign with Boomi. This is not a cheap product but well worth it if implemented and maintained in the correct and suggested way.
Take time to analyze and plan your integration before starting the development, know what you should do and have a clear idea of how you will do it before is very good to not get lost with the many ways that a process can be developed to meet a certain business case. From my experience with Boomi it is not so much the question “Can this be done?” that is the important one, but rather “How can we best do this?”.
Take time to analyze and plan your integration before starting the development, know what you should do and have a clear idea of how you will do it before is very good to not get lost with the many ways that a process can be developed to meet a certain business case. From my experience with Boomi it is not so much the question “Can this be done?” that is the important one, but rather “How can we best do this?”.
A powerful platform and tool for any integration
What do you like best about the product?
I like that Boomi is working hard to improve aspects of the UI. This is a highly important task in my opinion, since the platform and development tool is cloud and browser based. Boomi is demonstrating that this is a high priority for them, and I am enjoying the UI improvements so far.
I also like that a process can be extended with custom scripting if the built-in functionality is unable to suffice.
My favorite part about Boomi is the ability to create RESTful web services. It is intuitive to develop them, and they are very effective.
I also like that a process can be extended with custom scripting if the built-in functionality is unable to suffice.
My favorite part about Boomi is the ability to create RESTful web services. It is intuitive to develop them, and they are very effective.
What do you dislike about the product?
To keep on point with the UI improvements, there are certainly a lot of mouse clicks involved when it comes to browsing for components and configuring shapes. However, some of this has already been addressed so it is obvious that there is a backlog for improvements with the Boomi Dev team.
I also don't like the fact that a Map can't be unit tested by itself. If there was a way to unit test a map on its own (by configuring the inputs or uploading a csv that contains inputs, for example. And a way to check the expected output of each.) I believe development would be 10x more effective and more defects would be caught before production.
I do not like that a new profile is generated every time a Salesforce operation is created. I would like the option to browse for a profile before one may be created.
I also don't like the fact that a Map can't be unit tested by itself. If there was a way to unit test a map on its own (by configuring the inputs or uploading a csv that contains inputs, for example. And a way to check the expected output of each.) I believe development would be 10x more effective and more defects would be caught before production.
I do not like that a new profile is generated every time a Salesforce operation is created. I would like the option to browse for a profile before one may be created.
What problems is the product solving and how is that benefiting you?
I work on a team that integrates with Workday, Salesforce, Jive and Coupa quite a bit. Most of the Workday integrations consist of generating a flat file of some sort ( which Boomi is extremely effective with). Otherwise, integrations with Jive and Salesforce utilize their robust and effective web services.
The benefits of course with the Salesforce connector are the ability to use their web services without really coding at all. The query operations are easy to use (most of the time) and the update/create, etc. operations are even easier.
The benefits of course with the Salesforce connector are the ability to use their web services without really coding at all. The query operations are easy to use (most of the time) and the update/create, etc. operations are even easier.
Recommendations to others considering the product:
Although I would always recommend exploring your options, keep in mind that Boomi and the Atomsphere development tool is entirely in the cloud. That is tough to beat in my opinion.
Heading in the right direction
What do you like best about the product?
Capable of complex data transformations and is capable of a wide berth of use cases. Support can be very helpful and responsive. There have been several instances where we've had mission critical breakdowns and support has been awesome in putting in the hours until we got it figured out.
Their Revision History is great, especially when you're first learning the platform or want extreme version control. There's a lot of little places where you can do some major damage and having great version control mitigates development time. It's not listed as a connector, but it will work with Microsoft Dynamics Great Plains 2015 and eConnect 2014 which was nice (they do need to update the documentation for this connection though).
We had a mission critical integration that used a scripting component to sort data that would break every time there was a major update. Eventually, Boomi gave us a resource to help re-engineer the process so that it worked more in line with their development road map. This went a long way in fostering good will.
Their Revision History is great, especially when you're first learning the platform or want extreme version control. There's a lot of little places where you can do some major damage and having great version control mitigates development time. It's not listed as a connector, but it will work with Microsoft Dynamics Great Plains 2015 and eConnect 2014 which was nice (they do need to update the documentation for this connection though).
We had a mission critical integration that used a scripting component to sort data that would break every time there was a major update. Eventually, Boomi gave us a resource to help re-engineer the process so that it worked more in line with their development road map. This went a long way in fostering good will.
What do you dislike about the product?
Sometimes seemingly simple needs turn out to be very complex problems, eg sorting line item detail records on the header master record. Editing and creating custom XML profiles can be tricky, fortunately the Revision History component is fantastic. Connector management could be better, the same connector with a different ID won't deploy if you're at your cap, a problem which happens more often than you would imagine due to the strange and dangerous ways you copy processes and components. Getting at the root cause of an issue is often like peeling an onion.
What problems is the product solving and how is that benefiting you?
The primary intent of getting on the Boomi platform was to create a bi-directional sync between our Salesforce org and our instance of Great Plains which runs on a dedicated hosted server. With the some of the automation we've been able to realize using Boomi and various other applications has been profound, but when platform stability threatens that it can be harmful to our organization.
Recommendations to others considering the product:
Consider it carefully. If you're a small shop it can easily become your biggest administrative burden, but it can save your organization time with it's enterprise connections.
showing 381 - 390