select DASHOH.OH_Name,OACL_OH_Idnr,OACL_Lnr,OACL_AuthType,OACL_AuthIdnr,OACL_BitCode,OACL_Prohibition,USROH.OH_NAME, USR_FirstName || ' ' || USR_LastName as USR_Name, USR_EMail1from OH DASHOHleft outer join OACL on DASHOH.OH_IDnr = OACL_OH_Idnrleft outer join USR on OACL_AuthIdnr = USR_OH_Idnrleft outer join OH USROH on USR_OH_Idnr = USROH.OH_Idnrwhere 1=1and DASHOH.OH_OType = 'DASH'and DASHOH.OH_DeleteFlag = 0
delete from OACL where oacl_oh_idnr=...
1. Display the OACL table row for the private dashboard. In this example, the dashboard is named UC0.MAL.PRIV.DASH.
select oh_name,oh_client,oacl.*from oh,oaclwhere oh_idnr=oacl_oh_idnrand oh_name='UC0.MAL.PRIV.DASH'and oh_client=1and oh_deleteflag=0
One row should be returned.
2. Delete this row from the OACL table. In this example, the object ID number of the dashboard, and the ID uniquely identifying the row in the OACL table, is 1931002.
delete from oaclwhere oacl_oh_idnr=1931002
You should see a message indicating that the row was successfully deleted from the OACL table.
1 row deleted.
3. Commit the change to the DB.4. Restart the Automation Engine server.
I suppose if you were leery of deletes you could add your own id to the acl through sql.
I created a new idea for this problem. If you agree with the idea, please vote for it.Fix implementation of private dashboards feature, or remove this feature
I had a similar issue, a user was able to create a private dashboard named with a name that should not have been allowed by Automic, JOBS or JOBPLAN i think it was, that caused other issues, had to delete with SQL as the user was out of office.