Asset 360 Suite > Known Issues and Limitations > Asset Hierarchy-Related Known Issues and Limitations
Asset Hierarchy-Related Known Issues and Limitations
The following are the current known issues and limitations:
Data Load Limitation: It is recommended that you add the asset hierarchy component under a different tab on the lightning record page. This ensures that the hierarchy data load time does not stop user interactions with the other components in the default tab.
Data Volume Limitations:
In the Asset-Only hierarchy, a root asset can have 10,000 child assets. This limitation is in line with the SFDC limits.
In Account > Asset and Location > Asset hierarchies, each root node (account or location) can have 10000 records attached to it.
Hierarchy views can be plotted up to 20 levels. This limitation is in line with the SFDC limits.
If a node for which the hierarchy view is plotted has around 10,000 sibling records, it might take around 10 seconds to load the view. The same amount of time is taken when you expand a node too.
If an admin-configured filter is added to a hierarchy configuration when there are already two user-configured filters, all three filters are shown as active and applied. If the user disables any one filter among the three, it is cached in the browser, and only two filters are allowed to be active after that time.
In Account>Asset hierarchy, the search for the second word in the record name succeeds only for the starting and ending characters of the second word. For example, for an asset named Acc1-RootAst, the search text Root or Ast succeeds, but the search text ootA does not display any result.
If a user-configured filter is created for the Asset object for the Asset-Only hierarchy, it is not applied for the Asset object in the Account>Asset hierarchy for the same record. However, Admin-configured filters are applied.
Was this helpful?