Have static or excluded attribute not change the trends limits

As verified with tech support, static and excluded AF attributes effect the trend limits when chosing the "database limits" option. Static attributes have a min and maximum automatic limit of zero, so if you put them together with PI Point attributes in a single scale trend, the bottom y-limit will be forced to zero using the "database limits" option, even if the PI Point/PI Point attributes lower limits are above zero. So if you want to show horizontal line of 5,for example, in a trend, that will force the lower limit of the trend to 0. Excluded attributes also cause the same thing, so when using collections or context switching, the limits of trends for elements with excluded attribute get messed up. In this case not event adding minimum and maximums to AF help. Doesn't seem logical, in a functional perspective, that a non-zero static attribute or excluded attribute have a zero limit in a trend that takes effect. Current workaround is using custom limits in PI Vision. It would be great to either have control over this, or not have static/excluded attributes effect limits when used with other attributes in a trend.