Hi, as part of our initial testing of speckle workflows, we have been investigating pushing an entire revit analytical model to ETABS and this has worked fine.
However, when we have tried moving a handful of columns in ETABS and then sending just those columns to Speckle, when receiving these as an update in Revit, the columns do not move and instead it creates new columns in Revit.
I’m not sure if we are understanding the Speckle workflow correctly, but we ideally want to be able to send isolated updates rather then having to send the whole model.
I’ll let @bjoern provide a better explanation and solution to your workflow (as soon as he feels better ), but in the meantime I can explain what’s happening.
Going ETABS > Revit > ETABS is what we call internally “roundtripping” and that’s not supported as when an object/element enters a new BIM/Structural tool becomes essentially a new entity and it would be extremely unreliable trying to modify it and bring it back into the source app.
The current update mechanism Speckle support is only for A > B exchanges, so you could keep sending from ETABS to Revit (or vice versa) and our connectors will update elements that were received before (if IDs match).
Hi @teocomi, thanks for getting back to me and the explanation - makes sense.
Are there any connectors/workflows that do allow for ‘roundtripping’/ or is not supported at all on the Speckle platform?/ is there future scope for this to be supported?
), but in the meantime I can explain what’s happening.