30 Character Limit on Supporting References

Content

We recently discovered that there is a 30 character limit to the values that populate a Supporting Reference so certain values are getting cut off. I can't find this limit documented anywhere and am wondering what the intent was behind it. I would have assumed that the supporting reference would inherit the limit from the source. In this case it would 100 characters for an alphanumeric source. Can this limit be adjusted in the future or is the 30 character limit a hard stop for performance or other reasons?

For background on the use case, we have a subledger that has an account description and subaccount description that are always reported on together. The combination of these 2 fields (via a User-Defined Formula) will sometimes exceed 30 characters. Our current work around is to split the 2 fields into 2 separate supporting references.