There is room for improvement in the developer experience, particularly for those who are SQL proficient, as having more direct access would be beneficial. Additionally, configuring Semarchy xDM requires understanding xDM principles, and some backends like SQL Server lack features such as regex, unlike Oracle or Postgres.
Independent Software Consultant at a tech services company with 11-50 employees
Consultant
2020-11-22T15:44:38Z
Nov 22, 2020
They need to make the workflow more enhanced or dynamic in its functionality. That was the tiebreaker between Profisee and Semarchy - the client had a SQL server development environment and they could do a lot of stuff using the SQL server SDK to do complicated dynamic workflows. With Profisee, it wasn't impossible, however, it was a little bit more complicated to do. Semarchy is working on making it possible. I almost don't want to even say that that would be room for improvement, as I know that they're working. They may have already solved it. They could put a little bit more energy into out-of-the-box reporting. That was one of the things that I saw in Profisee that wasn't even really marketed that much. I wasn't even looking to their reporting features until I implemented it. At that point, I was like, "Oh my gosh, look at all this out-of-the-box data quality reporting that's going on! I don't have to necessarily go out and build all these reports from scratch." I was pleasantly surprised to see that in Profisee. I don't know that Semarchy has put the energy into that. They may have, but it certainly not to the extent that the other solution did.
What is master data? Master data is the crucial, all-important data that all businesses rely on to function on a regular, day-to-day basis. It is the core data at the heart of the business process and describes the relationship of the environment and how it relates to the complete business process. Master data encompasses all the data used throughout the entire business process life cycle. It can include - but is not limited to - such relationship processes as: clients (both internal...
There is room for improvement in the developer experience, particularly for those who are SQL proficient, as having more direct access would be beneficial. Additionally, configuring Semarchy xDM requires understanding xDM principles, and some backends like SQL Server lack features such as regex, unlike Oracle or Postgres.
They need to make the workflow more enhanced or dynamic in its functionality. That was the tiebreaker between Profisee and Semarchy - the client had a SQL server development environment and they could do a lot of stuff using the SQL server SDK to do complicated dynamic workflows. With Profisee, it wasn't impossible, however, it was a little bit more complicated to do. Semarchy is working on making it possible. I almost don't want to even say that that would be room for improvement, as I know that they're working. They may have already solved it. They could put a little bit more energy into out-of-the-box reporting. That was one of the things that I saw in Profisee that wasn't even really marketed that much. I wasn't even looking to their reporting features until I implemented it. At that point, I was like, "Oh my gosh, look at all this out-of-the-box data quality reporting that's going on! I don't have to necessarily go out and build all these reports from scratch." I was pleasantly surprised to see that in Profisee. I don't know that Semarchy has put the energy into that. They may have, but it certainly not to the extent that the other solution did.