- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2023 03:46 AM
Hi folks,
Client is asking for us to remove some duplicate Entity records from sn_grc_profile table.
When I delete the entity, it stays deleted until "GRC audit daily data run" and "GRC Daily scheduled data collection job" jobs run. At that point, the record gets recreated with a new sys_id and no information other than Vendor name.
Has anyone else encountered this in the past? What is the correct process to permanently delete an Entity record?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2023 08:49 PM
Hi @gk93 ,
Even if you delete it from Entities, it won't get deleted as you have to delete it from the source table.
As if you can check on Entity filter, you are using a table where your entities are coming from. So, to meet your requirement, either you delete it from the table itself(which is not recommended as you might be using that somewhere else) or second approach is you can limit it in the entity filter itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2023 08:24 AM
I think what you wrote and what you are asking is slightly different. I think you went back to the source table and deleted the duplicate from there. Now the question is what to do about the record in the sn_grc_profile table - which is the entity.
I have never tested this - so you may want to test it. I THINK that what will happen the next time the scheduled job (GRC Profile Generation) runs that the entity will be deactivated and any risks and controls related to it will be retired. I don't think you will have to manually delete the entity - but I could be wrong. From an audit perspective, once an entity has been generated and had controls or risks related to it - you don't want to delete this (at least not in production). It is possible that the entity is no longer relevant BUT could have been relevant in the past. And an auditor might want to know what happened to the entity in the past.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-23-2023 08:49 PM
Hi @gk93 ,
Even if you delete it from Entities, it won't get deleted as you have to delete it from the source table.
As if you can check on Entity filter, you are using a table where your entities are coming from. So, to meet your requirement, either you delete it from the table itself(which is not recommended as you might be using that somewhere else) or second approach is you can limit it in the entity filter itself.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2023 05:45 AM
Hi @gk93 ,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2023 05:46 AM
Hi @Community Alums,
I appreciate your response! This was definitely an entity created in error; we could deactivate it and apply filter but this is data that shouldn't be on the platform. All dependencies have been disassociated from the incorrect Entity record and transferred to the correct Entity. I've deleted the duplicate GRC profile but still have the second Entity appearing on the list. Any idea why?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2023 05:31 AM
Hi @gk93
Sandeep is correct. But you shouldn't be getting duplicates unless there are duplicates in your source table.
If there are duplicates in your source table then is there is some difference between those records where in the course table they are not really duplicates? If so, that difference needs to be used in the filter such that there will only be a single entity generated.
