How erwin DM NoSQL handles primary key _id in two different scenarios?

MongoDB primary key is represented as _id, but in our environment, we have a naming standard of resourceId for our PKs. One of the teams uses JavaDB mapping to map _id to resourceId, so I would want to see resourceId instead of _id in my model. Another team just ignores the _id field and creates another field named resourceId and gives it the UUID data type (which doesn't exist in the tool). How would I handle these 2 different scenarios in erwin DB NoSql tool?

Answer:

MongoDB primary keys are stored as _id. This is currently marked as an “objectid” typed field. With respect to UUID related fields, UUIDs are stored in MongoDB as a “binary” type field with a subtype (\x03 and \x04) indicating it is a UUID. When we reverse engineer this type of field, it will show up as a type of “binary”. In both cases the two teams would both have a _id and a resourceId field, but we will look into enhancing support to show the subtypes.