We have upgraded to 9.1.03 recently and the legacy CMDB Reconciliation Console has been removed. The problem is that we are not able to define precedence Sets using the Atrium console. In the Reconciliation Job editor when creating a new Activity (in this case a merge activity), I try to create or modify the Precedence Association Set but the config window is blank and I am not able to build the precedence set. Has anyone seen this issue or know why it's not working? Here is a screenshot of what we see.

I've checked with the team & they appear to have disabled the AR User Tool side for the feature. It would be possible to use the Remedy Developer Tool to open some of the back-end forms, but it wouldn't allow you to see the Console & they would all have to be manually updated, which can be prone to errors.

So at this point, the only way to do Precedence settings will be through Mid-Tier in which you have to create a custom Recon job & in the Merge Activity, you can create a new Precedence setting. It'll open a window where you can create one & add in the details. Here are the details to get started:

I believe in the future versions, being introduced from 9.1.04, they'll be modifying/using a different GUI interface that may make it easier to setup Precedence settings. If you have a test system, you may want to install CMDB 9.1.04 so you can see those features.

Alternatively, if you would like the AR User tool to be brought back into Remedy, you may suggest it as a feature request within BMC Communities. Here are the details on how to do that:

Hello. Has this issue been addressed? It recently popped up in our environment as well, after being able to set Precedence information properly via the Atrium Core Console as late as last summer. We haven't applied any patches or anything to Atrium CMDB in that time period so I'm hoping there's a hotfix or something available.

I did. Is there any particular thing I should be looking for? It looks like there's a lot of unrelated data appearing in the logs, so I might need to turn off other logging going there to see if anything shows up.

I have been utilizing a dummy recon job that has the merge function to modify precedence if/when needed and have not heard of another hotfix yet - but we are still on v9.1.03.001. Maybe the newer versions have a solution.

For each match, set the Precedence Explicit* field to be "No" and save it.

Restart arrecond

That took care of it for us. The same area of interest in the KB article Hector provided applies, but it's a different angle that we ran into the issue with. The underlying issue seems to be that there's a way RE:Group records get bad data in them (we believe ours happened in the process of importing records from another environment) and the Flex screen can't handle that bad data well even though the underlying Reconciliation Engine can.

I'd be curious to see if this approach helps anyone else or if there's other types of issues that can appear with RE:Group records.

Shawn, this seems to have done the trick. Not sure how those records were missing the data since they were all out of the box records and have never been updated. I wonder if this was introduced during a past upgrade that we just missed when testing. Either way it is working now, so thanks for the assistance.