Appian vs Microsoft Dynamics 365

• I have observed after version 17.1 we have a lot of good features in Appian that improve usability (UX). This adds real value in this competitive Digital space.
• You can understand business use case and convert it to a logical process automation.
• Process Modeller has improved a lot and providing smart services use adds more value.
• Service integration helps us to seamlessly integrate with third-party systems

Read full review

• Some useful out-of-the-box features, like mass uploads of Leads from trade shows or when qualifying a Lead, CRM automatically creates the Opportunity, Contact, and Account for you, etc.
• Really powerful customizations through the user interface to improve user experience. Things like Business Rules, for example, if Field A = 1, then Field B = 2 and Field C = 2, if Field A = 2, then Field B and Field C don't apply, so automatically hide them.
• Or other functionality that improves user experience, like Business Process Flows. These walk users step by step through our business process, helping them know when certain actions should take place, and at what point other data is now required. We've used this extensively with our Lead to Opportunity to Quote to Order process, helping users understand the business process each step of the way.
• Customizations built on top of the platform now called model-driven PowerApps. You can have connections to "typical" data, like Accounts, Contacts, or Opportunities, for example, but then connect that data to custom entities, records that only apply to your specific business. This is all done through the user interface and allows you to customize and automate specific line-of-business applications for your specific needs.
• Behind the scenes, D365 CE is built on SQL. So the data conforms to industry standards and makes it much easier to interact with. Your developers and IT team will thank you.

Read full review

• Advanced functionality requires use of the Appian expression language. The more advanced the logic, the harder it is to build with the expression language. This means development expertise is more relevant if you need advanced functionality, which I imagine applies almost all the time. I would much prefer if they allowed some common language such as JavaScript out of the box.
• Debugging has proved difficult. It’s easy for developers to get the app to or feature to a “working” state but it needs robust alpha testing.
• Deployment can be tricky. When a solution gets big and there are many teams and dependencies, it needs a careful process to ensure things don’t break.
• Reasuability of Appian objects is both a pro and con. Reusing objects across apps may be more trouble than its worth because of creating heavy dependencies. Experience is helpful to strike the right balance.

Read full review

• Microsoft Dynamics 365 storage & license cost can prohibit some large deployments or even cost-sensitive small projects from using the platform (although I'm certain most deployments would realize a positive ROI if implemented correctly with process automation).
• The cost and licensing document for Dynamics 365 is 61 pages and will take a rocket scientist to understand it. It's better to just have your Microsoft help estimate the cost if they are willing to help you that.
• The documentation on how to first fully understand the Out of the Box default solution and settings is lacking or even non-existing. This has the potential to derail Dynamic 365 launches and implementations from the gitgo. Want to use an out of the box entity?.. well it's probably related to 5 other entities that require configuration and full understanding of it to successful implement. And you ask where is the laymen guide or instructions?... User groups and forums. In Summary, Microsoft can up its game in deployment training and supporting documentation.
• Microsoft needs to incentivize more external platforms to build app connectors for easy integration, such as ZenDesk, Slack, Tableau, etc. Even the current connector apps such as Salesforce, MailChimp, Docusign are useless or don't work at all.
• Several limitations inhibit successful Dynamics 365 deployments such as: limited number of Rollup field calculations (summarizing fields on child/related records), limited number rows that can exported to Excel via advanced find, Dynamics 365 files, log and database storage size limit is extremely small and will always require purchasing additional storage (for Online deployments).
• New user buy-in or acceptance or system platform changes can be difficult if a solid change management plan isn't enacted.
• Don't expect much help from Microsoft on implementation or solutions unless it's a technical flaw with the platform. Microsoft relies on their MVP partner network to consult for implementations at a hefty cost. Hiring a knowledgeable and savvy Dynamics 365 System Administrator can reduce the need for consultant support; of course, this is dependant upon many many variables.

Read full review

• Currently we have no negative impact. We have a better follow-up on our tasks and we believe that tasks are completed faster.
• However we don't finish every project and we can't realy calculate our ROI. It's hard to give you some numbers.

Read full review

• It is hard to say, the reason why we are using Microsoft Dynamics CRM is because it is provided to us for free.
• It could be worthwhile to investigate whether an alternative CRM (even though paid) can be used to boost the ROI

Read full review