Inline Editing for Salesforce Reports: How to Update Records Faster
By Andreea Doroftei
January 04, 2022
The ability to edit multiple records directly while reviewing them is a feature that both Salesforce professionals and users appreciate. Available in both List Views and Reports, inline editing is a powerful tool that can greatly enhance productivity and streamline daily tasks in Salesforce.
In this article, we’ll explore how to use inline editing in reports, along with key considerations to keep in mind when making these updates.
What is Inline Editing?
Inline editing is the ability to change the value of a field without needing to navigate to an individual record. This translates into being able to update record values from somewhere other than the record page, usually a list of records, such as a list view or report. The ability to do this has multiple benefits including fewer clicks and greater user adoption of features.
When this functionality was initially made available as part of the Summer ’21 release, it was great to play around with, but there were a limited number of field types that could be edited. Salesforce has made considerable effort to improve upon this, and in following releases, many more fields became available, as you’ll discover below!
What is a Salesforce Report?
Standard Salesforce reports are something every admin and most users are accustomed to building day-in and day-out to visualize the data in various ways.
Reports represent the analytics base of Salesforce, as well as a dynamic, user-friendly and much prettier alternative to pivot tables and many Excel formulas. Until recently, they’ve been the key way to view Salesforce data. However, reports only allow you to view data, not amend it.
One of the most frequent user questions I bump into is definitely “How can I export my Opportunities to update each one in Excel?”.
This presents several problems. For a start, we don’t want users editing data outside of Salesforce! Second, the ‘Export Reports’ permission does not offer granular control over which objects can be exported, therefore with this permission, a user could export any report and its data if they had access to the report. In order to avoid a possible data leak, the alternative was to recommend a list view be used to update various Opportunity fields.
With the right permissions assigned, users are able to edit certain fields for up to 200 records at a time.
There are a few drawbacks to prompting users to use list views:
Without the ‘Manage Public List’ view permissions, they can’t be shared.
Users who do have the ‘Manage Public List’ views permission can edit/delete all existing public list views from any Standard or Custom object (yikes).
List views are less frequently used than reports and often less familiar, resulting in an adoption effort.
Check out the other limitations based on field type and object here.
Inline Editing in Reports
The limitations around list views, as well as a huge demand to improve native reporting capabilities, did make inline editing within Salesforce reports a dream come true.
With the release of this new functionality, Salesforce upped their user experience game considerably and capabilities have been expanded with subsequent releases. Hopefully, more improvements are to come, but that remains to be seen.
Setup Inline Editing in Reports
Enabling Inline Editing for Salesforce reports entails just checking one checkbox within the Reports and Dashboards Settings page in setup. Permissions to view and edit records and fields are conditioned by the usual mechanisms, respectively object and field access, as well as layout visibility.
So even if you turn on the setting, your data is safe and sound as this functionality will be completely dependent on the users’ already existing level of access.
What Can be Edited within Reports?
Perhaps the first use case that comes to mind is editing Opportunities as if you were a Sales Rep. With multiple Opportunities in their pipeline, your colleagues in the Sales team might be the happiest to hear that they can easily make tweaks while reviewing their items. Picklist fields such as Stage or even Opportunity next steps can be amended by whoever has access to the Opportunity, the fields, and has them on the layout. You can find a list of all currently available data types which can be edited here.
Additionally, most objects are available for inline editing as well, making this a functionality applicable to all teams using Salesforce – from Sales to Support and Marketing.
Not only are most field types available for inline editing within reports, but the feature itself can also easily be enabled with the click of a button every time inline editing is needed!
As you noticed above, multiple values across different records can be modified and will be committed to the database only after the user clicks Save. Additionally, fields dependent on any of the other fields being changed will be displayed as “Pending” and the value will reappear once editing is done or the page is refreshed. Even though I didn’t edit the amounts, the sub-totals do show as Pending as other changes might have impacted the calculation in the end.
User Enablement
One of the benefits of using reports is that user adoption is likely already pretty high. Your users are already familiar with creating and using reports, therefore adoption of inline edit for reports should be a piece of cake. It’s going to add extra functionality to something they’re already doing, but with fewer clicks!
Updating the ‘Next Step’ on an Opportunity might prove crucial for Sales Managers to know exactly how the deal will be progressing. Instead of opening individual Opportunities and searching for the field on the layout, Sales Reps can now open the report from their team’s dashboard and enter their notes while even making use of a chart to better filter records.
For more complex organizations, another huge advantage will definitely be the ability to better isolate data with the use of cross-filters in reports, which is not an option when using list views.
Note: Another thing reports and list views have now in common is that editable fields will have the pencil appearing when hovering over them, while non-editable ones will display a lock. This will ensure that users won’t spend time trying over and over again to make a change.
Salesforce Reports Inline Editing Use Cases
Seamless Record Updates
Inline editing in reports isn’t just for the Sales team! The inline field edit can be a time saver for Support and Marketing teams as well. For example, if the Marketing team is using Salesforce Campaigns, there’s surely at least one dashboard used to track performance or perhaps other KPIs.
With this new functionality, marketers don’t have to drill down into the individual records anymore and then return to the report. Instead, they can make adjustments to the key fields as they go.
Note: Fields used within reports as groupings are not available for inline editing.
Data Correction
This feature is also hugely beneficial for myself and my fellow admins. When troubleshooting different automations triggered by value changes, such as a boolean or perhaps a date, we typically use a report to measure the impact by the number of records.
As long as the field permissions are in place and the field isn’t marked as read-only on the layout, records can be edited one by one to do such testing without having to open 20 tabs and switch between them – if that’s not making our lives easier, I don’t know what is.
Considerations
As with any functionality, there are a few considerations to keep in mind and to check when promoting this feature. Let’s go through a few of them:
You can edit a maximum of 12 fields per record and a maximum of 100 fields across the entire report before saving.
Polymorphic fields are not supported and neither is the Opportunity Amount.
Columns associated with junction objects, such as Campaign Member, are not supported either.
Since things may change over time, make sure to take a look at the official documentation prior to making any implementation decisions.
Summary
Inline editing in reports is a powerful feature that can boost user adoption by allowing users to stay within Salesforce rather than relying on external tools like Excel.
If you’re new to Salesforce or want to dive deeper into Reports, be sure to explore Salesforce’s dedicated Trailhead modules for more learning opportunities.
The Author
Andreea Doroftei
Andreea is a Salesforce Technical Instructor at Salesforce Ben. She is an 18x certified Salesforce Professional with a passion for User Experience and Automation.
Thank you for this article! I am reviewing the implementation of the feature at org I work for, and noticed one difference between behavior and what's described in the note part - I observed that custom date fields have pencil icons and it's possible to add a date, however, Save button is greyed out. Looking at release notes, custom date fields remain non-editable, so a lock icon should appear. Were you able to test that bit?
Hello Margo,
Thank you for the comment! I have indeed tested this out in my developer org within an Opportunities report, editing a custom Account date field. I have done this again now and worked without a problem, the save button wasn't greyed out when saving.
The confusion might come from the fact that Custom Date/Time fields are not available for inline edit in the Summer '21 release notes, but as part of Winter '22 they are no longer mentioned as a limitation at the bottom of the page. I can't speak for the org you are working in so I would suggest you check out the limitations mentioned in the Winter'22 release : https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_reports_inline_editing.htm&type=5&release=234 , for example it might be the one relating to fields within object which doesn't have record types enabled.
Let me know how it goes, this is a really nice feature to implement :)
Hey Andrea,
Thank you for checking this! I realized that the issue was because the date field I tried to update was placed on a separate tab in Lightning App Builder (still within same object record page). After I moved the fields on the page layout to the default tab, I was able to edit the fields in the report. I wasn't aware of this limitation, since the Page layout did include the fields, but they were split in separate tabs.
Maybe I am missing something, and need more testing, but if this is the case, then probably we'll need to wait for further feature improvements :)
Hey Margo,
Really appreciate you getting back to me on this one as it is indeed a strange behavior. I will also try to replicate it and do more testing, which is obviously something I would recommend you continue doing as well. As far as the example I used while writing the article, this still works as expected in accordance to the Winter'22 update and all custom field edits within reports (date,boolean,number, etc.) that respect the release notes guidelines could be saved with no problem on Accounts, Opportunities and a custom object from a managed package (tried different objects to cover more examples).
Depending on your findings during testing, you can then make the decision to turn this on or not for your particular org. As you can imagine, we can speak to the general functionality but the implementation of it will always be dependent on what you have in your Salesforce org.
Hello Andreea,
Thank you for this article! Most fields works well but I can't edit rich text field. This is a custom field. Is there a limitation on rich text?
Hello Yvonne,
Glad you enjoyed the post and happy to hear the functionality is working well for you!
Indeed, Rich Text fields remain a limitation for inline editing within reports. There isn't a mention about this in the Spring'22 release notes, but hopefully it will be in the Winter'22 ones.
Hey Chava,
Glad you enjoyed the piece! There is, and permissions are based on field level security (granted through either profile or permission set), the presence of the fields on the layout as well as access to Record Types where applicable. Practically, the edit access piece has many similarities to the list views and having the pen next to the field on a report is an indication that it can be edited inline.
I stumbled upon a similar issue today. I had a checkbox on my report. I was able to edit the checkbox but the Apply button was greyed out. i found that I needed to add the checkbox field on the record's page layout to be able to make an update to it on the report. This is strange as I would not expect the requirement of the field to be on the page layout for the inline report update to work.
Hey Michele!
I agree it is a bit out of hand, hopefully this will be made a bit easier in future releases as the functionality becomes more and more widely used.
We have inline editing enabled in our org.
While updating the ‘Next Steps’ field of Opportunity, clicked on the pencil icon next to the 'next steps' field, and entered some value in the text field.
The ‘Apply’ button is still greyed out and we're not able to save.
Any suggestion on this is appreciated.
Hey TG,
Do you by any chance have multiple Opportunity Record Types? Are you using the standard Text field Next Step from the Opportunity or is it a custom one you're trying to edit?
Have you tried replicating this behavior in a sandbox or developer org as well? I have just went into a random Opportunities report and edited the Next Step standard field without a problem.
Hi,
I have a question that I am having trouble finding the answer to. I would like to enable Inline Editing for Reports in my Org, but I need to be able to limit it to certain fields, and certain users. Does anyone know if this is possible yet, or if it is on the roadmap? Thanks.
Hey Charles,
Happy to hear you're exploring in-line editing - at this time however, the feature can be enabled for the entire org only. There isn't a way for it to be enabled based on an user, role or profile.
As far as making it available only to certain users, the way you can do that to a certain extent is to control the access through field level security. This means only giving certain users edit access to certain fields, and they will be able to edit them (as long as they're supported) in reports as well.
Of course there are fields such as the Opportunity Stage which a lot of folks have access to edit, hence there isn't a lot of granular control. Hopefully this explanation helps, maybe Salesforce will allow this to be better controlled in further releases.
So here's a weird one. We wanted to see if we could inline edit campaign member status in a 'campaigns with campaign members' standard report type. We found it was locked and I figured it was because campaign member status is a little funky field. My colleague then asked the implementation partner that she works with and they added a custom field onto campaign member, added it to the report, and suddenly campaign member status is editable. Is this a weird known workaround? I have tested by removing the random field, saving the report, and inline editing goes away but when i add it back, it is available again. I know that I've been doing salesforce for way way too long and i'm definitely a few bananas short of a bunch but this one is blowing my mind.
Hello Shelly,
It is, but I don't believe it is in the sense that you're looking for. The in-line editing is enabled at org level, and in order for supported fields to become editable, the user should have write permissions on them through either the profile or permission set.
So for your specific use case, if it works to remove the write permissions for the fields who shouldn't be edited neither through in-line editing in reports nor through the individual edit pages from records, that would be the way to ensure users won't be able to edit.
Hello Brenda! That is definitely weird - I have indeed noticed that Campaign Member status was locked on the report page, but considered it was because of it being a funky field hence a limitation. Out of curiosity, I have tried the "workaround" with the random custom field (I chose to create a picklist on the Campaign Member) but sadly I couldn't replicate the behavior you noticed. This could be a workaround, but at least in my developer sandbox it didn't work :(
Hello Viktoria
Happy you enjoyed the article! This is actually something I tried when writing the article, and I found that it wasn't available to edit int he report run page (I did not have record types enabled in my developer edition, and the field was on the layout assigned to my profile). Went into that environment now and enabled Record Types just to test this out, and it is still not supported apparently. Since I couldn't find any documentation specifying more details yet regarding the Opportunity Amount (or standard currency fields) being a limitation for in-line editing, let's hope it will be part of future releases.
In the meantime, what I have done in my sandbox was to create a custom amount field and that one was editable, so even if it's not anywhere close to ideal this can be used as a temporary workaround if it is business critical for in-line editing to be available, then the value in the custom field can be used to populate the custom field with a flow.
I have the feature enabled. I have a Campaigns with Opportunities report set up with url-based dynamic filtering.
Sometimes when the report loads, the fields are inline-editable.
Sometimes they show as locked with a message: "Inline editing isn't supported for this cell"
This is the exact same report, filtered for the exact same records. I just hit the browser refresh button and it changes from editable to locked.
Perhaps this is why it's a beta feature.
Is it possible to mass update the same field for multiple records at the same time without clicking through one by one? For example, in a list view, I can select all cases or select multiple cases at one time using the Shift key. Once selected, I could select the field to edit, make the change, and have an option to update only that single record or all selected cases.
Is this available through the report in-line edit feature?
Hello Jimmy! This is something I was curious about myself, but sadly this is not something available with in-line edit in reports, or at least not yet. The only way to edit multiple records on the same report run-page now is to individually modify the fields for each of the records. There is also no mention in the documentation either for being another possibility at this time.
https://help.salesforce.com/s/articleView?id=release-notes.rn_rd_reports_multi_inline_editing_ga.htm&type=5&release=238
Playing around with it further and trying adding different custom fields, some fields did become editable. For me I added a checkbox field after which another custom field (picklist) that I wanted to be editable finally turned up as editable.
Is there any work around for enabling inline editing for long text fields? I know they are restricted, which is unfortunate since it would facilitate our process if we could.
How does inline editing on reports differ from inline editing on list views regarding the requirement to filter by record type?
My understanding is that inline editing will not work at all in a list view, unless the list view is filtered on record type. And that that's true even if there is only one record type on the object.
I do not notice that same restriction on inline editing for reporting, but I do notice that there are very few fields that are editable. Would more fields become editable if I filtered on record type?
Hello Oswaldo,
As of now, I am not aware of any workaround and editing long text fields remains a limitation. I will make sure to come back and update the post in case this will change in the future.
Thank you!
Hello Tiffany,
In my opinion, the reason why using in-line editing in a report versus a list view is the complexity of the filters. As you noticed in the article, I did mention the list views as well, and that is because indeed the functionality is quite similar.
You have to filter on the record type in both list views and reports, only if record types are enabled. If record types are not enabled on the said object, you can make use of the in-line editing in list views without a problem - if you'd like to confirm the behavior, you can spin up a new developer edition org, and try that out on the Opportunities (in-line editing works without.a problem, and there's no existing record type).
As far as the fields being available for in-line editing in reports, my recommendation is to always follow the latest documentation and changes Salesforce is sharing - since the first iteration of this functionality, more fields becam available, so I am guessing it is a matter of time until at some point the others will be as well. Additionally, there are record type, permissions and layout considerations as well.
Thank you!
Using the inline editing to clean up data from Classy (addresses, particuarly) has been a game-changer. Interestingly, I cannot edit the Mailing State/Province field, while I can edit every other mailing field (not a permissions issue). I CAN edit it in listview. Is this a known issue/limitation? Just curious. I have my own efficient way to deal with this, but eventually, I'll be passing on clean up to someone else and want to make it as easy as posisble for them. Thank you!
Hello Allison! Happy yo hear you enjoy the functionality, agreed it is definitely a game changer. So far, I haven't heard about a known issue pertaining to Mailing State/Province specifically, but I will test it out as well and let you know my findings, as according to the documentation "You can edit state and country/territory fields if state and country/territory picklists are enabled"
Unable to edit the checkbox field on the Reports as i m doing the inline editing , can you please help ,
checkbox has required access in terms of the FLS and its present on the Page layout.
Thanks In advance.
Comments: