MAM 7.6.1.2:

There is a system property called mxe.report.adhoc.editWithGroupAccess:
"Enable editing of Ad Hoc report when any security group has access to the report."

There is a Tech Note that talks about that setting: BMXAA7993E - This report cannot be edited because one or more security groups have access to this report...

"Since this setting is configurable, you can either leave it as "=0", because you do not wish other users, who also have access to this report, to modify it. Or you can change it to "=1", save. update, and this will give the users the ability to modify the report."

Question:
Does that blurb mean that all users who have security to see the report can edit the report? (in my case, everyone has access, due to the Share/Public checkbox being enabled)
Or is the wording just awkward, and only the creator of the report can edit it?
#AssetandFacilitiesManagement
#Maximo

QBRs only allow the creator to modify the report. You can change the created by field in the Report Administrator application so that another user could modify but only 1 person can have modify access at a time.

------------------------------
Steven Shull
------------------------------

Original Message:
Sent: Fri December 03, 2021 10:31 AM
From: User1971
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

MAM 7.6.1.2:

There is a system property called mxe.report.adhoc.editWithGroupAccess:
"Enable editing of Ad Hoc report when any security group has access to the report."

There is a Tech Note that talks about that setting: BMXAA7993E - This report cannot be edited because one or more security groups have access to this report...

"Since this setting is configurable, you can either leave it as "=0", because you do not wish other users, who also have access to this report, to modify it. Or you can change it to "=1", save. update, and this will give the users the ability to modify the report."

Question:
Does that blurb mean that all users who have security to see the report can edit the report? (in my case, everyone has access, due to the Share/Public checkbox being enabled)
Or is the wording just awkward, and only the creator of the report can edit it?
#AssetandFacilitiesManagement
#Maximo

Hello @Steven Shull, Does this feature also allow the user to modify the query that was originally saved on the report? I appreciate your guidance on this. 

------------------------------
Vandna Patel
------------------------------

Original Message:
Sent: Mon December 06, 2021 08:46 AM
From: Steven Shull
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

QBRs only allow the creator to modify the report. You can change the created by field in the Report Administrator application so that another user could modify but only 1 person can have modify access at a time.

------------------------------
Steven Shull

Original Message:
Sent: Fri December 03, 2021 10:31 AM
From: User1971
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

MAM 7.6.1.2:

There is a system property called mxe.report.adhoc.editWithGroupAccess:
"Enable editing of Ad Hoc report when any security group has access to the report."

There is a Tech Note that talks about that setting: BMXAA7993E - This report cannot be edited because one or more security groups have access to this report...

"Since this setting is configurable, you can either leave it as "=0", because you do not wish other users, who also have access to this report, to modify it. Or you can change it to "=1", save. update, and this will give the users the ability to modify the report."

Question:
Does that blurb mean that all users who have security to see the report can edit the report? (in my case, everyone has access, due to the Share/Public checkbox being enabled)
Or is the wording just awkward, and only the creator of the report can edit it?
#AssetandFacilitiesManagement
#Maximo

I can't explain why but we don't let the user modify the saved where clause of a QBR. We expect users to recreate a report when the where clause changes. That being said, if you modified the WHERECLAUSE attribute on the REPORTADHOC table and edited the report in some way, it would utilize the new where clause. Again, not officially supported but should work

------------------------------
Steven Shull
------------------------------

Original Message:
Sent: Fri September 20, 2024 03:16 PM
From: Vandna Patel
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

Hello @Steven Shull, Does this feature also allow the user to modify the query that was originally saved on the report? I appreciate your guidance on this. 

------------------------------
Vandna Patel

Original Message:
Sent: Mon December 06, 2021 08:46 AM
From: Steven Shull
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

QBRs only allow the creator to modify the report. You can change the created by field in the Report Administrator application so that another user could modify but only 1 person can have modify access at a time.

------------------------------
Steven Shull

Original Message:
Sent: Fri December 03, 2021 10:31 AM
From: User1971
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

MAM 7.6.1.2:

There is a system property called mxe.report.adhoc.editWithGroupAccess:
"Enable editing of Ad Hoc report when any security group has access to the report."

There is a Tech Note that talks about that setting: BMXAA7993E - This report cannot be edited because one or more security groups have access to this report...

"Since this setting is configurable, you can either leave it as "=0", because you do not wish other users, who also have access to this report, to modify it. Or you can change it to "=1", save. update, and this will give the users the ability to modify the report."

Question:
Does that blurb mean that all users who have security to see the report can edit the report? (in my case, everyone has access, due to the Share/Public checkbox being enabled)
Or is the wording just awkward, and only the creator of the report can edit it?
#AssetandFacilitiesManagement
#Maximo

Great thank you very much @Steven Shull for your update, really appreciate it. 

Thanks

Vandna

------------------------------
Vandna Patel
------------------------------

Original Message:
Sent: Mon September 23, 2024 09:05 AM
From: Steven Shull
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

I can't explain why but we don't let the user modify the saved where clause of a QBR. We expect users to recreate a report when the where clause changes. That being said, if you modified the WHERECLAUSE attribute on the REPORTADHOC table and edited the report in some way, it would utilize the new where clause. Again, not officially supported but should work

------------------------------
Steven Shull

Original Message:
Sent: Fri September 20, 2024 03:16 PM
From: Vandna Patel
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

Hello @Steven Shull, Does this feature also allow the user to modify the query that was originally saved on the report? I appreciate your guidance on this. 

------------------------------
Vandna Patel

Original Message:
Sent: Mon December 06, 2021 08:46 AM
From: Steven Shull
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

QBRs only allow the creator to modify the report. You can change the created by field in the Report Administrator application so that another user could modify but only 1 person can have modify access at a time.

------------------------------
Steven Shull

Original Message:
Sent: Fri December 03, 2021 10:31 AM
From: User1971
Subject: Ad-hoc report system setting: mxe.report.adhoc.editWithGroupAccess

MAM 7.6.1.2:

There is a system property called mxe.report.adhoc.editWithGroupAccess:
"Enable editing of Ad Hoc report when any security group has access to the report."

There is a Tech Note that talks about that setting: BMXAA7993E - This report cannot be edited because one or more security groups have access to this report...

"Since this setting is configurable, you can either leave it as "=0", because you do not wish other users, who also have access to this report, to modify it. Or you can change it to "=1", save. update, and this will give the users the ability to modify the report."

Question:
Does that blurb mean that all users who have security to see the report can edit the report? (in my case, everyone has access, due to the Share/Public checkbox being enabled)
Or is the wording just awkward, and only the creator of the report can edit it?
#AssetandFacilitiesManagement
#Maximo