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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Update data in Dataverse table using a Flow

(1) ShareShare
ReportReport
Posted on by 10
Hi,
 
I have created a table in Dataverse (Ticket) using columns from two other Dataverse tables (Backlog and Track). Backlog table has a column Assigned and Track table has a column Assignment. Backlog contains transaction data and Track has master data. My business requirement is that a flow should match Assigned value with Assignment value and if match is found then should update the related records in Ticket table.
 
Being new to this subject need help.
 
Regards
 
 
Categories:
I have the same question (0)
  • Suggested answer
    11manish Profile Picture
    718 on at
    You can achieve this requirement using Microsoft Power Automate with Microsoft Dataverse.
     
    Requirement
    Compare:
    • Backlog.Assigned (transaction data)
    • Track.Assignment (master data)
    If match found → update related records in Ticket table
     
    Best Approach (Power Automate Flow)
    Step 1: Trigger
    Use:
    • When a row is added or modified (Backlog table)
    Step 2: Get Matching Record from Track
    Use List Rows (Track table) with Filter Query:
    • Assignment eq 'AssignedValue'
    Replace with dynamic value from Backlog
    Step 3: Condition Check
    If matching record exists:
    • length(value) > 0
    Step 4: Update Ticket Table
    Use Update Row (Ticket table)
    Map:
    • Related fields from Backlog + Track

    Best practice hierarchy:
    • Use Dataverse relationships (Lookup)
    • Use Power Automate (if dynamic matching needed)
    • Avoid manual matching in app logic
  • Suggested answer
    ManoVerse Profile Picture
    1,154 Super User 2026 Season 1 on at
    As you are new with this , I am sharing below steps by step implementation you can do for your requirement : 
    Your Requirement
    Backlog table -> column Assigned (transaction data)
    Track table -> column Assignment (master data)
    Ticket table -> needs to be updated when:  Backlog.Assigned = Track.Assignment
    This is a cross‑table match + conditional update scenario, where Power Automate will help , you can design the flow as high level as below : 
     
    Trigger (Backlog row created or modified) - >  List rows (Track table – filtered by Assignment) - > Condition (Match found?) - > Update related Ticket record
     
    Step 1: Create the Trigger
    Go to Power Automate -> Create -> Automated Cloud Flow
    Choose trigger:
    Microsoft Dataverse – When a row is added or modified
    Configure:
    Table name: Backlog
    Change type: Added or Modified
    📌 This ensures the flow runs whenever new transaction data arrives.
     
    Step 2: List Rows from Track (Match Logic)
    Add action:
    Dataverse -> List rows
    Configure:
    Field Value
    Table name Track
    Filter rows assignment eq '@{triggerOutputs()?['body/assigned']}'
     
    *This uses OData filtering, which is much faster and recommended instead of looping all records
    Also this is Important
    • Use logical column names, not display names
    • Assignment and Assigned must be same data type (Text / Choice / Lookup)
    Step 3: Check If a Match Was Found

    Add Condition:
    length(body('List_rows')?['value']) is greater than 0
    *This confirms at least one matching Track record exists
     
    Step 4: Update Ticket Table
    Inside Yes branch:
    Add action:
    Dataverse -> Update a row
    Configure:
    Field Value
    Table name Ticket
    Row ID Related Ticket ID
    Columns Update as required (e.g. Status, Assignment Info)
    If Ticket has a lookup to Backlog, use the Backlog ID directly.
     
    Handling Large Data Safely  is important here
    If Track table has many rows:
    • Open List rows
    • Go to Settings
    • Enable Pagination
    • Set threshold (e.g. 100000)
     this will Prevents silent failures (very common beginner issue while using power automate)
     
    Hope this will help.
  • Sam70 Profile Picture
    10 on at
    Hi,
     
    There is a change in the requirement. We are not using Ticket table anymore. A lookup column has been added in the Backlog table and the Lookup table is Track. Pls. suggest the change accordingly.
     
    Regards
  • Suggested answer
    ManoVerse Profile Picture
    1,154 Super User 2026 Season 1 on at
    With the updated requirement, the logic is much simpler since the Track table is now a lookup on the Backlog table and the Ticket table is no longer used.
    The flow should trigger on Backlog create/update, find the matching Track record where Track.Assignment = Backlog.Assigned, and then update the same Backlog row by setting the Track lookup to the matched Track record.
     
    In short:
    • Match Backlog.Assigned with Track.Assignment
    • If a match exists, set the Track lookup on Backlog
    • No separate Ticket update is required anymore
    • Just ensure both columns use the same data type and the lookup is populated using the Track row ID.
  • Sam70 Profile Picture
    10 on at
    Hi,
     
    Kindly guide me on how to get Row ID
     
    Regards
  • Sam70 Profile Picture
    10 on at
     
    What can be the issue. created a GUID column in Backlog table
     
    Regards
  • Suggested answer
    ManoVerse Profile Picture
    1,154 Super User 2026 Season 1 on at
    It seems you are trying to update a lookup column using a text value (VaccinesDatabases-L2) instead of the GUID of the related Track record , lookup columns only accept GUIDs, not names or codes.
    Let me repharse your requirement and then we will go step by step:
    When a Backlog record is created or updated:
    1. Read Backlog.Assigned (text / choice / number)
    2. Find a Track record where
    3. Track.Assignment = Backlog.Assigned
    4. If a match is found
    5. Update the Lookup column in Backlog to point to that Track record
    You have backlog Table  with column [ Assigned (Text or Choice) , Track(Lookup of Track table) ]
    You have Track table with column [ Assignement ( Text or Choice) ]
    Note* : 
    Assigned and Assignment must be same data type , Values must match exactly (case‑insensitive is OK)
     
     STEP 1: Create the Flow
    Go to Power Automate
    Create -> Automated Cloud Flow
    Name:
    Backlog – Auto Associate Track
    Trigger:
    Dataverse -> When a row is added, modified or deleted
    Change type:
    Added or Modified
    Table name:
    Backlog
    Scope:
    Organization
     
    STEP 2: Prevent Infinite Loop ( this is IMPORTANT)
    Add Trigger Condition (Advanced settings):
    Go to trigger -> Settings -> Trigger Conditions
    @not(empty(triggerOutputs()?['body/assigned']))
    This ensures:
    Flow runs only when Assigned has a value
    Prevents unnecessary executions
     
    STEP 3: Get Matching Track Record
    Add new step → Dataverse – List rows
    Configuration
    Table name: Track
    Filter rows:
    assignment eq '@{triggerOutputs()?['body/assigned']}'
     This matches:
    Backlog.Assigned = Track.Assignment
     
    STEP 4: Check If Match Is Found
    Add Condition
    Left side:
    Length(body('List_rows')?['value'])
    Operator:
    Plain Textis greater tha
    is greater than
    right side:
    0

    STEP 5: If YES -> Update Backlog Lookup
    Inside Yes branch:
    Action: Dataverse – Update a row
    Configuration
    Table name: Backlog
    Row ID:
    @{triggerOutputs()?['body/backlogid']
    Track (Lookup column):
    Use this expression:
    first(body('List_rows')?['value'])?['trackid']
    This sets:
    Backlog.Track = Matched Track record
     
    STEP 6: If NO -> Do Nothing (Optional Logging)
    Inside No branch:
    Leave empty OR
    Add:
    Compose -> “No matching Track found”
     
    Hope this will help to you resolve your issue.

     

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

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 85

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 76 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 61

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans