Smartsheet Row Change to CRM/ERP Sync

Overview

This flow keeps Smartsheet aligned with the business system of record. On a 15-minute schedule it reads every row from an operational Smartsheet sheet, upserts each row into a Dataverse mirror table (flowlibs_crmordermirror), writes the resulting Dataverse record id back onto the Smartsheet row, and posts a notification to Microsoft Teams. New rows create a record; existing rows are updated in place (idempotent upsert keyed on the stable Smartsheet row id).

Why it matters: Teams track operationally in Smartsheet, but the business system holds the truth. Syncing changed rows avoids divergence and double entry, and the write-back of the record id gives each Smartsheet row a durable link to its system-of-record counterpart.

Use Case

A sales/operations team manages working items (orders, deals, projects) in a Smartsheet sheet with columns such as Item, Status, Amount, Due Date, and Contact Email. The business records of truth live in Dataverse (or a CRM/ERP fronted by Dataverse). This flow continuously reflects material Smartsheet changes into Dataverse, stamps each Dataverse record id back onto the originating Smartsheet row, and keeps the operations channel informed of every create/update.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Smartsheet	shared_smartsheet	GetSheetData
HHTTP	http	PUT /2.0/sheets/{id}/rows
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

CRM/ERP target

Swap the Dataverse mirror table for Salesforce/Dynamics by replacing the three Dataverse actions with the equivalent connector ops; keep the same upsert/write-back shape.

Field filter

Only sync material fields, or add a Condition before upsert to skip rows whose Status hasn't changed (compare incoming Status to the stored mirror record).

Event-driven

Replace the Recurrence trigger with the Smartsheet OnUpdatedSpecificSheet / OnRowCreated trigger for near-real-time sync.

Conflict log

Record mismatches (e.g. Smartsheet vs. Dataverse value drift) to an audit table.

Column titles

All read column titles are env vars, so the flow ports to any sheet by changing values only.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@concat('flowlibs_smartsheetrowid eq ''', string(items('Apply_to_each')?['id']), '''')

@empty(outputs('List_Existing_Record')?['body/value'])

@items('Apply_to_each')?[variables('varStatusColumn')]

@first(outputs('List_Existing_Record')?['body/value'])?['flowlibs_crmordermirrorid']

{ "id": @items('Apply_to_each')?['id'], "cells": [ { "columnId": @int(variables('varRefColumnId')), "value": @outputs('Create_Mirror_Record')?['body/flowlibs_crmordermirrorid'] } ] }

Customize & download