We've had a few cases where projects were upgraded on ACC and the BIM Manager forgot to go to Clarity and ugrade the project there and tasks just stopped running. Is it possible for Clarity to just do this on it's own?
Bumping this request...
Just spitballing here, but I think if you see a task on an ACC project fail because the model is the wrong version, try running the task again with the next newest version and if that works, update the Clarity project to that version. If it still fails, try the next newest version and so on until you find the right version or run out of versions to try.
Of course, notify the project coordinators/admins when this happens. Not sure how this works with Revit Server or File-based projects (maybe it doesn't), but in the near term, it's probably fine if this is a ACC project feature only.
Yes, I think just looking at the cloud workshared models. The BIM360/ACC project can only host one release and it reports that on the Docs > Settings > Revit Cloud Model Upgrade page. However, based on how that page loads, I suspect there's not a single api call that reports that value. I don't think you need to continuously check and since you already report when a task failed because of the wrong version, maybe you can piggyback on that failure and figure out the version at that time and then automatically upgrade the project on the Clarity side and rerun the task. Or maybe there's a different kind of notification to the admins that still puts that burden on us, but makes it harder to overlook... I'd still lean toward letting Clarity do that automatically for BIM360/ACC projects. I don't see a downside, but maybe I'm not considering every edge case.
Correct, no API (who knows why?). But it seems like something we can improve the experience on...
-Matt
Eric,
We can look into this...
It's possible - I'm just not sure how aggressively we need to watch it...
- Scan constantly for new Revit file versions, and try to detect what version they are? (presumably only workshared, not uploaded).
- Catch the specific error the first time it happens on the task server- and send a message to make it happen...
-Matt
