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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Restrict a field until approved by a power automate flow

(5) ShareShare
ReportReport
Posted on by 554
How can you set up a field in BC from being edited (i.e. restricted) until it has first been approved by a power automate flow to update it? I don't want to block the card on which it sits.
For example, say I want to update a vendor's bank details or I want to change the default bin code for an item but I want to first restrict the user from updating the field on BC and then having the power automate trigger.
 
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    6,540 Super User 2025 Season 2 on at
    Good morning, afternoon, or evening depending on your location!
     
    You can achieve this in Business Central by using Approval Workflows combined with Power Automate to restrict field editing until approval is granted.
     
    Steps to Restrict a Field Until Approved
    1. Set Up an Approval Workflow in Business Central:
      • Navigate to Workflows in Business Central.
      • Create a new workflow that triggers when a user attempts to modify the restricted field (e.g., Vendor Bank Details or Default Bin Code).
      • Configure the workflow to prevent changes until approval is received.
    2. Use Power Automate to Handle Approvals:
      • Create a Power Automate flow that listens for changes to the field.
      • When a user attempts to edit the field, trigger an approval request.
      • Once approved, allow the field update.
    3. Restrict Editing Until Approval:
      • Use Field-Level Security or Record Restrictions in Business Central to prevent unauthorized edits.
      • You can configure a workflow response to restrict usage of the record until approval is granted.
    4. Allow Editing After Approval:
      • Once the Power Automate flow completes the approval process, update the field using a Business Central API call or a workflow response to remove the restriction.
    Considerations
    • Granular Control: Ensure that only specific fields are restricted, not the entire record.
    • User Permissions: Verify that users have the correct permissions to request changes but not override restrictions.
    • Error Handling: Implement fallback mechanisms in case the approval process fails.
     
    Hope this helps some!
  • Suggested answer
    Jainam M. Kothari Profile Picture
    15,641 Super User 2025 Season 2 on at
  • Suggested answer
    Khushbu Rajvi. Profile Picture
    21,046 Super User 2025 Season 2 on at

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

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,810

#2
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 810 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 676 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans