Brief Summary: I have a CDT with near to 500 fields that holds some values and just to mentioned I am not using any nested CDTs. I'm using that CDT inside an interface to hold values. I am worried if the application could face any issues in the future if it grows larger. I would like to know even if I have more than 500 fields, is it safe to use that CDT in the application or is it causes any issues in the future. Note: I don't wish to proceed for partial CDTs by breaking the entire CDT into sub-CDTs. Please list down what kind of issues my application may face, if any, down in the comments. Please help me clearing this and I would be gratefully for your help, Thank you.

neeleshj2272

Question

Is it vulnerable to the application if a CDT has more than recommended number of fields (I have a CDT with 500 fields approx).

Forum|Forum|2 years ago
September 2, 2023
6 replies
0 views

Brief Summary:

I have a CDT with near to 500 fields that holds some values and just to mentioned I am not using any nested CDTs.
I'm using that CDT inside an interface to hold values.
I am worried if the application could face any issues in the future if it grows larger.
I would like to know even if I have more than 500 fields, is it safe to use that CDT in the application or is it causes any issues in the future.

Note:

I don't wish to proceed for partial CDTs by breaking the entire CDT into sub-CDTs.
Please list down what kind of issues my application may face, if any, down in the comments.

Please help me clearing this and I would be gratefully for your help, Thank you.

stefanhelzle0001

Brainy

I consider this to already be or at least become an issue on many levels. BTW, this feels like flawed requirements ...

What is the use case here?

Did you consider a key-value store?

neeleshj2272Author

[mention:126a676c85024855948336691b0a7b92:e9ed411860ed4f2ba0265705b8793d05] sir, I asked to my Friend and he gave me the use case: we have one large pivot interface (which has six different units and contains every day calendar field) where user fill data quarterly and for hold these values we created this more then 500 field CDT.

Note we are saving this data in external system so we use integration for insert and update.

stefanhelzle0001

Brainy

Then, why even bother using a CDT. When you exchange data via JSON, there is no need for a CDT.

mathieud0001

Brainy

That seems like way too many fields for 1 entity. Would be curious to know more to what led to such a decision.

neeleshj2272Author

[mention:f5e81b8502fa4e77ad12697686a4fc56:e9ed411860ed4f2ba0265705b8793d05] sir, I asked to my Friend and he gave me the use case: we have one large pivot interface (which has six different units and contains every day calendar field) where user fill data quarterly and for hold these values we created this more then 500 field CDT.

Note we are saving this data in external system so we use integration for insert and update.

mathieud0001

Brainy

Care to give an example?

Sign up

Login with SSO

Login to the community

Login with SSO