Microsoft Dynamics 365 for Finance and Operations (or Dynamics AX) was an ERP product in the Dynamics family. It has been split into separate Dynamics 365 products and is no longer available.
We used BizTalk Server as we had all other integrating applications developed on .Net and using Microsoft development environment. Kafka is best if integration is between non-Microsoft applications. We had few adapters developed using Microsoft .Net framework. BizTalk is well …
Microsoft BizTalk was chosen as the integration hub many years ago. It is still in use in a number of places in the organization however we are no longer developing specifically for this product in mind. We now develop in a number of places and if Microsoft BizTalk is the …
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution …
BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize …
Using this Microsoft platform is the similarity of the structure and appearance of the software and their integration and easy integration with each other, which makes the work easier for users and employees of the company.
Microsoft D365 FO stands out amongst the competitors with its strong backing on the Microsoft Azure cloud and the life cycle services is the best I’ve seen. There is a ways to go in making it low/no code and mobile is there but not great. Overall an ok product as ERP is a …
Cost and local regional compliance were primary factors in chosing Microsoft Dynamics AX over SAP Access Control for our need. SAP AC would have provided easier integration into our primary ERP system SAP but there were some regional compliance with ASEAN countries as well as …
I was not part of the decision making process to select Microsoft Dynamics AX, however, I do know that an exhaustive search was done and many options were considered alongside Microsoft Dynamics AX and I feel that the right decision was made in choosing this solution.
SAP--there is no way to compare these as SAP is large and complicated as it is not a single integrated system - but many system underneath the GUI / Cover of SAP. No process flexibility that is so needed in our competitive world where global competition requires change at a …
It is perfectly suited if some heavy operation needs to be automated where jobs can be queued up. Scalable app which is required to develop in a lesser time frame. Good for when users should be able to change rules more frequently without any downtime, like promotions. The server is well proven in the market. BizTalk server is the best fit if all other integration adapters are developed using Microsoft applications and if all applications are meant to be processed on a Windows environment.
It integrates fully with the other Microsoft software we use daily, and this coordination speeds up our work and gives us the agility to run easily. For example, in a purchase inquiry, the customer, after submitting a request, identifies the teams that should work on the project, and if they need further review by other people, they are added to the process, and everything is managed seamlessly rather than the sales process. Get the result as fast as possible.
BizTalk uses Microsoft Visual Studio as the IDE (integrated development environment) tool, and it's very easy to use.
The orchestration engine of BizTalk addresses resource issue very well for long-running business processes by dehydrating and rehydrating orchestration instances.
BizTalk is very easy to integrate if the development is mainly on the Microsoft software family.
BizTalk needs to be better at tracking down errors after the fact. Input files by default get deleted after processing successfully, unless you specifically specify that they don't. This can be an issue where you need to see what the input file contained, since you may have errors showing up in your target platform, in our case this was SAP.
BizTalk logging needs improved. It needs to be able to log the content of the messages it sends and receives. It would be good if the log had a link to the input and output files.
BizTalk needs to allow a simple way to preserve the input and output files for debugging purposes. A master setting on the orchestration would be helpful for this.
Sales Ledger. Currently, the idea behind the sales ledger module is that the company prepares a sales order for another company. I would prefer the developers consider the scenario where a sales order is prepared for the same company but for another branch or unit.
Postings of issues items are currently possible but none of the modules caters to "departmental material or item request". Further tweaks have been done on our Project Module to cater for this but it's not entirely perfect. This will enable aid in cost allocation per departmental request of materials or items.
Challenges with the bank module - does not allow for easily reconciliation as the statement from the banks can not be uploaded except for specific format.
Microsoft Dynamics continues to evolve by bringing more functionality to the customer. Also there are several independent software providers that offer a wide range of solutions for vertical markets.
Microsoft BizTalk is not an intuitive product. It requires many hours of looking through the settings to achieve what you need. Using 3rd party DLLs is a nightmare as you are forced to register them in the GAC of the server and this process is quite cumbersome just to use a DLL.
Overall the product does what we need it to do in order for us to function as a company. While there are some concerns over ongoing costs, the belief is, once we have it fully acclimated to our business the cost should settle into alignment with our original expectations. The new features that are consistently being added do add value to the product as they are usually customer request directed.
Some integration and high volume ramping challenges, particularly with BizTalk and SQL Server, but getting sorted out. Outages over time appeared to be more dependent on integration complexity than AX MES.
Some integration and high volume ramping challenges, particularly with BizTalk and SQL Server, but getting sorted out. Outages over time appeared to be more dependent on integration complexity than AX MES.
BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
We use a 3rd-party Microsoft Partner for the system. They are responsive and very knowledgeable. While costs have been mentioned several times in this review they are very aware of costs and have developers who are more economical they use to help offset the level of work required to meet our changes and fix our issues.
It took a lot of work, but Microsoft ultimately did a good job with in-person training, including being onsite in multiple global locations for extended periods.
Our solution deviated from a number of key out-of-the-box standards that were included in Online training. We just used that for introduction to the general functionality.
Some rough spots, but ultimately worked out. The contract didn't appear to be structured to support the level of overlapping facility deployments required to meet timeline commitments. Merging cultures on the program was also challenging. Overall, not an easy implementation by any stretch. Everyone did the best they could.
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution you wish, whereas Jitterbit is much more limited.
Cost and local regional compliance were primary factors in chosing Microsoft Dynamics AX over SAP Access Control for our need. SAP AC would have provided easier integration into our primary ERP system SAP but there were some regional compliance with ASEAN countries as well as the cost of implementation was more over Microsoft Dynamics AX.