web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
Your Invited to Keeping It Real with the Power Platform
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Microsoft Power Up Program Community / Built a free Chrome ex...
Microsoft Power Up Program Community
Unanswered

Built a free Chrome extension to update hidden D365 fields

(2) ShareShare
ReportReport
Posted on by Kar Nall 14

Hello everyone,

Need your Feedback.

I always have to leave the D365 record page if I needed to update a field that isn't on the form, like XrmToolBox, go into Power Platform, export to Excel, or build a Flow just to change one value.

So I built a chrome extention for this purpose.

D365 Field Editor is a free Chrome extension that loads every field on a Dataverse entity record directly in a side panel  not just the ones visible on the form.

You can search, edit, and save values without leaving the record page.

What it does:

- Opens as a resizable side panel on any D365 record

- Loads ALL fields for that entity

- Search and filter by field name, logical name, or type

- Edit and save directly via the Dataverse Web API

- Handles all field types

- Uses your existing browser session

🔗 Chrome Web Store:

https://chromewebstore.google.com/detail/d365-field-editor/mdaalaeelapjdhefiedbmdonciiafbfp

It's my first Chrome extension so I'd genuinely love feedback. If you hit any edge cases with specific field types, please let me know

unnamed.png
Categories:
Power Apps
I have the same question (0)
  • Sunil Kumar Pashikanti Profile Picture
    Sunil Kumar Pashikanti 1,688 Moderator on at
     
    This is honestly a fantastic tool. It solves a major pain point that most of us just accept as “part of the job” when working with Dataverse. The friction of having to leave a record, open XrmToolBox, or temporarily add hidden fields to a form just to make a quick update is a real productivity killer. Having this functionality inline on the record page is a massive win.
     
    What really stands out:
    • The Side Panel Approach: It’s non-intrusive and keeps the focus on the data.
    • Logical Name Search: Being able to search by both display and logical names is a huge time-saver for power users and devs.
    • Metadata Access: Loading all fields, not just those on the form, is where the real value lies.
    • Session Security: Leveraging the existing authenticated session is the smartest way to handle security and deployment.
    A few things I’d be curious to see tested:
    • Security & FLS: Does the panel visually respect Field-Level Security? (Even if the API blocks the write, a "read-only" UI indicator would be a great safety feature).
    • Complex Fields: How does it handle polymorphic lookups (like Owner or Customer) and Choice sets?
    • Performance: How does it behave on "heavy" entities like Account or Contact with hundreds of custom fields?
    Ideas for future updates:
    • A "Show Only Empty Fields" filter would be a dream for data cleanup tasks.
    • A quick "Copy Logical Name" button for when you're writing scripts or Power Automate expressions.
    • A clear "Environment Name" indicator to prevent those "oops, wrong environment" edits.
    The Bottom Line:
    This feels like a lightweight, agile alternative to XrmToolBox for quick fixes. It fills a gap in the native Model-Driven App experience that Microsoft hasn't addressed. For a first extension, this is incredibly solid work. I can see this becoming a staple in every admin’s toolkit.
    Great job!
  • Kar Nall Profile Picture
    Kar Nall 14 on at
    Thank you @Sunil Kumar Pashikanti for your feedback, if was very helpful and detailed.
     
    The extension currently respects metadata-level permissions on the fields marked as non-updatable in the entity metadata show as read-only in the panel. how ever the Field-Level Security is not yet visually indicated. If FLS blocks a write, the Dataverse API will return an error
    and the panel will show the error message, but it won't proactively warn you before you try.
     
    polymorphic lookups (like Owner or Customer) are currently excluded from the editable fields list because they require special handling they can point to multiple entity types which needs a different approach than standard lookups. They show in the panel as read-only so you can see the current value. This was on my future roadmap.
     
    Tested on Account and Contact which have 300-400 fields. The metadata fetch with no issues on first load for heavy entities, then subsequent navigation to the same entity type is faster since the entity set name is cached in memory.
     
    Please let me know if any thing i need to address in my subsequent release.
     
     
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities
Your Invited to Keeping It Real with the Power Platform

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Microsoft Power Up Program Community

#1
Sunil Kumar Pashikanti Profile Picture

Sunil Kumar Pashikanti 27 Moderator

#2
MH-03032028-0 Profile Picture

MH-03032028-0 18 Microsoft Employee

#3
11manish Profile Picture

11manish 15

Last 30 days Overall leaderboard

Featured topics

Introduce yourself!

Product updates

Microsoft Power Platform Community release plans