Increase the Scalar Properties limit of an EntityType

One-sentence summary of your feature request?

Increase the maximum limit of 128 Scalar Properties per EntityType so it can support larger data models.

Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.

An EntityType is currently limited to 128 Scalar Properties. In some client contexts, this limit is reached very quickly and becomes highly restrictive—especially when the source data models are large or complex. This forces technical workarounds to meet the constraint, which complicates the implementation and moves away from a faithful, natural representation of the real data model.
The idea would be to increase this maximum limit so that EntityTypes can better reflect richer data models, without having to rely on artificial workarounds.

How do you currently solve the challenges you have by not having this feature?

Because of this limit, it is necessary to implement technical workarounds (for example, restructuring the model, splitting properties across multiple EntityTypes, or giving up certain properties) in order to stay below the 128 Scalar Properties threshold. These workarounds add complexity and do not allow large data models to be represented faithfully.

Hello @EnaelleDcs

I can see the challenge, although one could argue that 128 scalar properties should already cover most use cases and that not every attribute necessarily needs to be exposed through a single EntityType.

In many implementations, multiple EntityTypes are used to achieve a clearer separation and better logical grouping of data. Since NIM acts as an abstraction layer, creating and managing relationships between multiple EntityTypes is generally straightforward.

If I remember correctly, the 128-property limit may originate from underlying technical or database constraints. If that is the case, increasing the limit might be more complex than it appears.