Asset Tree
Exceeding the limits, no real problem

Overview

If you try to show too many children assets, you may run into a note that you have exceeded the limit. By default, the limit is 500 child assets per parent asset, so if you have 501 or more – you will see the 1st 500 and a message that you exceeded the limit.

Under normal circumstances, you shouldn't run into this limit. If you have that many child assets, typically you should add another layer to section the asset into subsections.

But sometimes, when pulling child assets from another system, such as a GIS, it may be too much work to split them, you may have decided it is 'best' to just dump 100's of children onto one asset.

Why is there a limit?

The more data sent to the client, the slower the server will be, the more bandwidth consumed, the more battery consumed (yes a very tiny amount), the slower the client speed is, and scrolling through hundreds of children is not efficient.

So what do you do?

We give several options for you to reasonably deal with this:

  • Change your asset structure if you have manually done this and the problem is irrelevant.
  • have your import process put the 100's of assets into categories each containing a more reasonable number. (With no offence if you disagree with the use of 'reasonable')
  • Change the criteria, so that the GIS assets are not returned for everyone other than the people who need them.
  • Just change the limit. If you are finding you have 521 maximum, you'd change the limit to 550 instead of 500.
  • On the other hand, if in your system "The only time we have more than 15 is when we have 100's that we don't care about", then you can lower the maximum to 20 (or whatever makes sense) so that we won't bring back 100's when it makes no sense.

Repeating the least obvious answer:

You may not care about assets in a branch that has more than <you fill in the number, default 500> child assets. Maybe 'any time there are more than 50, they are assets that, for my job, I have no interest in any of them'. In that case - set the query to limit it to 50. Set the limit high enough so that, 3 years from now, when you care about one that has 23, you don't only see 20. So if you think "I will never care if there are more than 15" you might want to set the limit at 20 or even 100 to be safe. Because you can be pretty sure you will forget that you set this limit!

How to change the # of rows returned in a query

Look for a property in the query that looks like this:

  "maxRowsOffline": 250,

And change the number to whatever number you want.

Note that the pattern is:

(
"<property1>": <value>,
"<property2>": <value>,
...
"<propertyN>": <value>
)

Note that they may be shown in one very long line. That's OK.

Note that the values, if a number do not have " characters around them.

Note that all but the last property has a comma , at the end to separate it from the next property.

Note: Do not remove the front or end brackets (...) and don't add more.