Hi,
Short story: (need to control hiding certain fields in reports + controlling the ability of users to customize dashboards, and add columns in standard/custom reports)
As ERPNext is growing rabidly, and many customers are joining the family, an important issue is emerging as urgent topic to solve, that is the reports permissions field level.
For instance, all of our customers are demanding stock reports to be shared with all of their team members (sales to know what to sell, warehouse keepers, procurement to know what to reorder,…) but they don’t want most of these users to know the item valuation rate, but there is no easy way to do it, so we guess updating this feature is an urgent need at this stage for reporting.
Here is how I tried preventing showing the value for one user.
Opened a standard report called “Stock Balance”. It has columns related to values.
I removed all the stock value related columns and saved report as “Just Stock Balance”.
Went to tool called “Role Permission for report manager”. Ensure that original Stock Balance report is accessible only to (say) Manager. Stock User only had access on the new report.
In my test account, user doesn’t custom button at all. The permission for report edit and write is given to very few. Please ensure in your account also, All role has only read permission on the reports.
This solved one part of my similar problem (Thank you), but the users are still able to use add column to add in valuation column. This is after disabling prepared report is there a workaround to it.?
I tried with client script to hide the button class, it doesn’t seem to work on report page, or i have not correctly defined the script.
@umair Dear, would you please help in this issue, it has becoming a urgency for most of my customers, if there is a straight forward solution without coding would be great.
Did you find a solution to this ? I actually thought you could try changing the permission level (perm level) of the field in the source doctype (probably Stock Ledger Entry in your case)
In our case, we need to ignore user permissions on certain fields in specific reports. This also seems not to be available and leaves us with the need to build separate versions of reports that already exist
I think we really do need more granular permission controls for reports now
@szufisher would be very nice if we could get that documentation in English
Hi, sorry for the delay, I just noticed, yes actually we made a special application based on field Perm Level, that would prevent users from adding a column in reports (all types) unless they have a required Perm Level for that specific field.
issue solved for my customers
