Skip to main content
Question

Matching Proposals Usability

  • March 6, 2026
  • 0 replies
  • 32 views

Hi everyone,

we are in the middle of our project where ataccama consumes business partner (customer and vendor) records from various source systems. We apply currently the consolidation style, but intend to switch to a coexistnece style later. So, when collecting many records from various source systems, we end up with a bunch of matching proposals who need to be reviewed by our Data Stewards in ataccama. That’s our setup.

I’m struggeling a lot with the quite limited functional approach ataccama is following when it comes to dealing with the matching proposals. In our case we only have a handful of columns which are displayed in that user interface. A lot of IDs, a summary column (which we cannot filter), and some other columns which are honestly of no use. I always try to put myself into the position of a Data Steward who is now faced with the task to resolve the matching proposals. And what the Data Steward finds is a user interface that is as far away from the term user-friendliness as one can imagine. A Data Steward is not responsible for all the matching proposals - the summary column contains information that he/she could use to narrow it down to those records the Data Steward is really interested in. But for that column - which offers the highest value - filtering is not even an option.

How do other customers tackle this? Is there any chance to alter that situation? Any idea/suggestion/solution would be helpful.

I have the impression ataccama is capable of many things and a powerful solution, but from a usability’s point of view, it’s a nightmare for Business users.

Cheers, Penny