Your Smartsheet schedule and BuildingSwell now share a hierarchy

Indented rows on a Smartsheet schedule now come into BuildingSwell as a real tree, and a tree you build in BuildingSwell is written back to the sheet with the same nesting. Phases and components sit under their order on both sides instead of arriving as a flat list.

Each row carries its own detail rather than borrowing the order's. A phase or a component keeps its own name, due date, cost code, assigned people, tags, project and route, so a nested row on the sheet says the same thing the deliverable says in Planning.

Whoever has children owns the shape. If a row already has child rows on the sheet, applying a route in BuildingSwell will not expand a second structure beside them: the sync leaves the row as it is and says so in the activity log. The same goes the other way: re-indenting a row in Smartsheet after it has synced leaves the BuildingSwell tree unchanged, and the run summary lists every row that moved, so both sides can see where the structures differ.

Connection errors also read like what actually happened. A failing sync used to report the same sentence whichever call broke; it now names the request, how many times it was retried, and what the other side answered, so a problem at Smartsheet is no longer indistinguishable from a problem with your credentials.