Cannot save operation representative when there are a lot of contacts

[fviduya]

Description of the Tech Debt

During registration of operation, when there are a lot of contacts (tested with 300 contacts), operation representative cannot be saved.

This is displayed in the console:

Tech Debt Triage

The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level	Value
High	3
Medium	2
Low	1

Technical Debt - Risk Types	Level	Value
Business Area Risk - Risk of business area visibility / damage to user experience	0	0
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it	0	0
System Fault Risk - Risk of system errors or application downtime	0	0
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?	0	0
Time Sink Risk - How much will this tech debt slow the development process down	0	0
TOTAL SCORE:	0	0

Development Checklist:

• Checklist item
• Checklist item
• Checklist item

[fviduya]

Hi @patriciarussellCAS / @vesselak tagging for visibility.

This issue prevents user from registering an operation because it doesn't allow an operation representative to be saved when there are a lot of records in contacts page. I replicated this locally, I started from 50 records and incremented by 50 until I failed to register an operation - locally that happened after having 300 records. I can do some test again in the environment. This might be edge case scenario as realistically they might not have that much contacts per operator, but it is still possible to be encountered given that we do not limit the number of contacts.