Pushing Event Changes from BackOps Back to Flex

Write-back sends selected changes you make to a Flex-linked event in BackOps back to Flex Rental Solutions, so a date moved in BackOps does not have to be moved again in Flex. It is switched on per mapping row with the Push to Flex checkbox on the Event Sync tab of Settings › Integrations › Flex Rental Solutions. Set up event sync first.

What Can Be Pushed

Push to Flex is available only on these mapping rows:

• The Flex name, mapped from Event Name or a Text attribute
• Dates and times, from date and date-time attributes mapped from Flex date-time fields
• Status, from a Select attribute mapped from the Flex status, with a one-to-one value map

Nothing else is pushed: event roles, event type, other select attributes, crew and collaborator references, template inputs, static values, and contacts all stay one-way from Flex. BackOps never creates new records in Flex.

How Pushes Run

Pushes run as part of event sync. An edit goes out on the first event sync that runs at least two minutes after the event was last edited, so the timing follows your sync interval. Push runs that send changes or raise warnings appear on the History tab as Event Push runs. Turning on Push to Flex for the first row does not send past values; only later edits are pushed.

Flex date-times are treated as UTC in both directions, so a time pushed from BackOps arrives in Flex as UTC.

Pushing Status

Flex changes status through its workflow, so a status push runs a Flex action rather than writing the status directly. For each BackOps status you want to push, choose the Flex action to run from each starting state. At least one action is required before status can be pushed. Clearing the status in BackOps is not pushed; the run records a warning instead.