This topic includes up-to-date information about any known issues related to Ideate StyleManager.
See Performance Tips for suggestions on how to reduce the processing time for certain methods.
The ‘Edit’ button sometimes displays the Properties palette instead of opening the Edit Type dialog. This applies to tools that use the Properties palette to display type information including: Scope Box, Dimensions, Text, etc. The current workaround is to first select something in the current (non-schedule) view and then pick the Edit button again.
Unable to delete root (parent) linked CAD Imports
The ‘Delete’ button is currently enabled for deleting the root (listed in bold) of the linked CAD import style. When picked, a warning will appear, but even after selecting ‘Yes’ the style will NOT be deleted by Ideate StyleManager. See this topic for more info about how to clean up Imported Object Styles.
In Revit 2022, if the line style assigned within the MEP Settings>Hidden Lines dialog is a custom line style, and that style is then deleted, the Revit project will become unstable and crash. We have reported this to Autodesk. Until this bug is fixed in Revit 2022 you should not Analyze or Delete that line style via Ideate StyleManager.
Sketch lines of filled regions will display in the Usage pane only if they are custom line styles. If they are built-in styles they cannot be determined and will not be displayed in the results. See section about ‘reserved’ Line Styles.
If the border of cells that are part of the schedule header (not the title) are overridden with another line style, the process of Analyzing that line style will cause the cell border to revert to Thin Lines. This is an API bug that has been filed with Autodesk. The workaround is to not override these cell borders. The borders that are part of the title (or above) are not impacted by this issue.
Line Style usage within a group cannot be merged due to Revit API limitations.
The Line Pattern assignments for Halftone/Underlay are currently not reported as usage by StyleManager. — Fixed in June 2022 release.
Some files will display multiple versions of the same fill pattern. While it is not possible to create a duplicate-named fill pattern using the Revit user interface, it is possible via the API. In these cases, we recommend that you use the merge or delete functions to fix these conditions. On occasion we have seen a duplicate of the built-in fill pattern called <Solid fill>. We do not know the source of this condition but we have enabled the merge and delete buttons for these duplicates even though the delete function is typically not available for a built-in style. These special weird duplicates are flagged by Ideate StyleManager with an asterisk as shown. We recommend that you use the delete function on any “<Solid fill>[Name]*”. This will remove the duplicate and force any referenced element to revert to the true built-in <Solid fill> pattern.
Note on the screenshot, the ‘correct’ built-in pattern has “-” usage and no “*” after the name.
Material usage within a group is not yet supported for merge.
For some joined wall conditions, the merge process cannot complete and will trigger a Revit error. We recommend that you use the Cancel option within the Revit warning. The results will show that the usage was not replaced. To resolve this error, select the wall/floor/ceiling type from the Usage pane, and use the Edit Type button to manually swap the material.
If a material is assigned to a view filter and this material is later deleted or merged, the affected properties in the view filters will reset to (none). Fixed in June 2022 release.
Material appearance assets have no ‘default’ status in Revit, so in order to delete assets we recommend selecting one or more assets and then using Merge to assign them all to another asset. During this process the older assets will be removed from the project properly and any materials referenced by the assets will be assigned to the newly assigned asset.
There are no known issues related to view templates. Let us know if you have a support issue related to view templates.
There are no known issues related to viewports. Let us know if you have a support issue related to viewports.
Selection type filter returns an error when ‘Edit Overrides’ is picked in StyleManager. As a workaround, please open ‘Visibility Graphics/VG’ directly in Revit to edit the overrides. — Fixed in Revit 2022 release.
If a scope box is assigned to a view filter and this scope box is later deleted or merged, the affected properties in the view filters will reset to (none). — Fixed in June 2022 release
Merging scope boxes may result in (logical) Revit errors. Be careful when merging scope boxes that do not overlap. Let us know if you have other support issues related to scope boxes.
Scope box usage within a group is not yet supported for Merge.
In models originally created in Revit 2016 or earlier, some Stair Path Types would have no value for the Stair Path Type>Text Type parameter. StyleManager is unable to show this ‘blank’ usage.
Review the Stair Path types with the help of Ideate Explorer, or use the Fonts tool to check that the Stair Path types show on the usage list for the expected text type. Any file with this condition present would not have the Stair Path listed as usage for any Font.
Populating the text type list takes too long: During this process Ideate StyleManager compiles the list of all fonts present on the PC. This process can take a disproportionate time if the default printer is not accessible. As a workaround, please change your (Windows) default printer when working with Text types.
‘Font Not Found’ warning when the casing of the font name does not match the name in Windows: In certain scenarios the font names stored in Revit can have different casing than the fonts in Windows. (example: "romand" vs "RomanD") The fonts render correctly in Revit, but the “Text Font” type parameter will be blank. This condition could be caused by the project being started in a very old version of Revit, as newer releases force the correct casing to be used. To resolve, edit the Text Type and assign an available font.
Populating the font list takes too long: During this process Ideate StyleManager compiles the list of all fonts present on the PC. This process can take a disproportionate time if the default printer is not accessible. As a workaround, please change your (Windows) default printer when working with Fonts.
Merging a dimension style that uses a ‘Continuous’ Dimension String Type into a style that uses a ‘Baseline’ Dimension String Type is currently not supported. The user will see a Revit Warning dialog and the action will be rolled back with no changes made to the model. Merging a Baseline into a Continuous string type Dimension style is supported.
There are no known issues related to arrowheads. Let us know if you have a support issue related to arrowheads.
Ideate StyleManager support for parameters includes all parameters except for built-in parameters (e.g. Mark, Type Mark, etc.) and any family parameters that are not shared. Also, the usages for any parameter that is referenced by the P&ID mapping are not able to be detected due to a lack of Revit API.
Merging parameters is not yet supported in Ideate StyleManager. In the future we may support merging of parameters that have similar Data Types and Parameter Types. See below for important data considerations and tips.
In the example below there are three shared parameters all called “W” but the first one has a Data Type of Mass per Unit Length while the other two use Number. Merging these will not be possible due to these differences. Additionally, the 2nd “W” is defined in the family as a Type-based parameter, while the 3rd “W” is defined in other families as an Instance. In this case we also do not want to merge the instance data into the type data as values would be lost in transit.
You can use Ideate BIMLink to copy/paste values from one parameter to another, assuming the pasted values are appropriate for the parameter data type (text vs. length).
Only Global Parameters and Key Schedule Parameters can be renamed via Autodesk’s Revit API. You can vote for better access to the Project and Shared Parameter APIs here.
There are no known issues related to global parameters. Let us know if you have a support issue related to global parameters.
Thank you for taking time to inform us about a bug or feature request.