Microsoft Dynamics 365 | Integration, Dataverse...

Hit column limit on Case (incident) table - looking for long-term design options

(4) Share

Report

Posted on by CU06100827-0

Hi everyone,

Not too long ago we received an error saying we’d reached the maximum column limit on the Case (incident) table. We already have a large number of custom columns, Business Process Flows (BPFs), and forms.
We can delete some columns and possibly consolidate a few BPFs, but we don’t see that as a long-term solution. The incident table is very dynamic in our operations, and we’ll continue to need new fields and processes.

What’s the best approach to handle this? We’re considering creating a new custom table related to the incident table, moving some existing case types and their processes there (important: we can't lose any historical data), and then creating all new columns and processes on the new table. Practically speaking, is this possible? How much effort would it take, and what level of technical competence is required? If there’s an easier or more sustainable approach, we’re open to suggestions.

Thanks!

Categories:

Dynamics 365 general

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

PerezAguiar Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hey!

The same way that INcident Table also has IncidentClosure for example, perhaps this might be the best approach: Additional tables with relationship

Regards,

Was this reply helpful? Yes No
CU06100827-0 23 on at

Like (1)

Report
Copy link

Link copied!

@PerezAguiar - do you know how we should think regarding to the relationships? Like is there any kind of documentation regarding this?

Was this reply helpful? Yes No
ManoVerse 760 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

This is interesting , you have reached to 1000+ column limit , what are the pointer which are enforcing you to create new fields and column , i think there are better approaches but need to understand the requirement so that we can understand why so many columns are required, why columns cannot be managed commonly , you must need some dynamics configurations by which you can handle different approaches and fields data.

Was this reply helpful? Yes No
Suggested answer

Tom_Gioielli 3,078 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
In the words of Ron Burgundy...

I'm not even mad. That's amazing.

In all honesty, if you have hit the 1,000 column limit in a single table I think your design requirements and existing feature is a bit beyond what many of us will be able to assist with in some comments on the Community forums. I would highly recommend finding a Microsoft Partner to work with who can sit down and come up with a plan that addresses several things:

Column and process consolidation

Business process improvements

Architectural updates to your CRM environment to support the requirements

Reporting needs and updates

You probably have ended up shoving too much into the case table and will need to break it up into multiple tables. This can be done with parent/child relationships, or by creating separate records for each "stage" your case works through. With some thoughtful design and an eye towards reporting, it should be very doable to break this up.

Was this reply helpful? Yes No