View & Sheet Updates
Sheet renaming in Revit does not automatically update in Pirros' card view, though the updated name will show once you open the detail.
The parameters of details are tracked for the purposes of managing PirrosInSync. That means if the sheet number of a sheet has been changed, then all the details on that sheet will no longer be in sync because the sheet number parameter on the detail has changed.
Best practice: Reopen the detail in Pirros after renaming the sheet in Revit to confirm it reflects correctly.
Duplicates & Change History
Syncing can sometimes result in duplicate details, particularly if:
The project settings for the model has changed. If the model is assigned to a new project, new copies of those details will be uploaded associated with the new project.
Multiple versions of the same detail exist due to inconsistent sync strategies
This may lead to loss of change history between versions.
“Recently Changed Views” Behavior
This section in the plugin shows all out-of-sync items, not only views changed recently.
Global model changes, such as family updates can trigger a need to sync many unrelated details.
Different Sync Strategies Used by Teams
Always-on Syncing: Some firms sync continuously to stay up-to-date. This may cause too much noise with constant email updates.
Scheduled Syncs: Others sync monthly or quarterly as part of a routine QA process.
Selective Syncing: Some teams only sync details relevant to current projects.
Encourage users to pick the method that matches their workflow and complexity.
Recommended Best Practices
Sync both detail and sheet together using the same change message to keep history clean and reduce redundancy.
Check “Recently Changed Views” regularly, especially after large model updates.
Establish a sync rhythm, whether it’s project-based, time-based, or continuous. Document this in your internal workflow.