Removing (or renaming) a private event causes an error and fails to complete

[MichaelAivaliotis]

I created a private request. When I select to remove it using the DQMH tools, it generates an error message (LV2023- v7.1.0.1503):

When I check the event cluster, I see the private event reference is still there (circled in red):

This is reproducible by creating a new module, then creating the event and then trying to remove it. The only other event I created before this was the "Private.private-WFR" also shown in the image. When I try to remove that one it blocks me with a message that you cannot remove the last private event. I'm not sure I understand that limitation, but that's getting off-topic.

Update:

I'm seeing a similar but different message appear when trying to rename a private request. This time I created a private request in a new module, then tried to rename it. without any prior requests created.

[Gregory]

Hi Michael, I don't have a solution, but I was able to reproduce your issue in LV 2016 with DQMH 7.1.

One thing I noticed is that within the "Request Events--cluster.ctl" there used to be a cluster called Private. (Maybe from DQMH 6?). If I try to remove a Private event within the Private cluster, it works fine without error.

Now, in DQMH 7.1 the private event refs are in the main cluster, their name is just has "Private." as a prefix. When I try to remove one of these, I get the same error you showed.

[mbaudot · Accepted solution]

Thanks for reporting this. I created Issue #1007 internally. We'll provide more info as soon as we have.