200 Attributes is the limit

kklosson

It seems I've hit the attribute limit of 200. Ironically, I only need about 5 more. Is there a technical or practical reason for this limitation?

And yes, I do how how to normalize a database - believe me, this BO needs about 210 attributes. In addition, it has about 15 related child BO's.

To resolve this, I'll have to somehow parse out some topical areas into another BO. From the usability standpoint, it will break the operating paradigm and will behave rather funny.

Any chance of increasing this a bit in the future?

kklosson

The more I look at this issue, the more it becomes a complete show-stopper for me. I cannot see any way to construct this application and present a reasonable usable navigation experience. Just imagine that you had a BO with 50 attributes and numerous child table relationships and a field limitation of 25 fields. How would chop up the fields in the main BO? Aware IM was clearly not made to work that way (nor should it be) but I'm absolutely dead in the water at this limitation. I realize it's more attributes than most BOs are likely to have, but that's what I've got.

I will need to know from Aware IM if this is resolvable please.

aware_support

This IS resolvable and it will be resolved in the next build. This is a leftover from the version 3.0 interface. The limitation is no longer necessary in version 4.0.

The next build will fix it and will be available some time this week.

kklosson

This is fantastic news! I continue to be very impressed to with your team's responsiveness. Absolutely first rate.

aware_support

This has been fixed in version 4.1