@forwardslashns/taskit-validation-messages 1.3.6 → 1.3.7

package/dist/validation/features/client-records-entity-states-histories.validation-messages.d.ts

@@ -7,12 +7,12 @@ export declare const CLIENT_RECORDS_ENTITY_STATES: {
     readonly NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
         readonly message: "The state, {domesticState}, starts on {domesticStateStartingDate}, which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the state or the client's date established.";
         readonly params: readonly ["clientDateEstablished", "domesticState", "domesticStateStartingDate"];
-        readonly affectedFields: readonly ["dateEstablished", "domesticStates"];
+        readonly affectedFields: readonly ["dateEstablished", "domesticState"];
     };
     readonly NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
         readonly message: "One or more states have a start date which is after the client's close date of {clientCloseDate}. {domesticState} starting {domesticStateStartingDate}. Please update the state/s start date/s to be before the client's close date, or update the client's close date.";
         readonly params: readonly ["clientCloseDate", "domesticState", "domesticStateStartingDate"];
-        readonly affectedFields: readonly ["closeDate", "domesticStates"];
+        readonly affectedFields: readonly ["closeDate", "domesticState"];
     };
     readonly DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
         readonly message: "Current Domestic State Starting Date cannot be Empty";
@@ -30,7 +30,7 @@ export declare const CLIENT_RECORDS_ENTITY_STATES: {
     };
     readonly AT_LEAST_ONE_DOMESTIC_STATE_SHOULD_EXIST: {
         readonly message: "At least one domestic state should exist";
-        readonly affectedFields: readonly ["domesticStates"];
+        readonly affectedFields: readonly ["domesticState"];
     };
     readonly STATES_STARTING_DATE_NOT_POPULATED: {
         readonly message: "Starting date for {state} cannot be empty";
@@ -55,22 +55,22 @@ export declare const CLIENT_RECORDS_ENTITY_STATES: {
     readonly DOMESTIC_STATES_DATE_GAP_DETECTED: {
         readonly message: "There is a gap in the timeframes between {currentState}, ending {currentStateEndDate}, and {nextState}, starting {nextStateStartDate}. Please adjust the dates to fill this gap.";
         readonly params: readonly ["currentState", "currentStateEndDate", "nextState", "nextStateStartDate"];
-        readonly affectedFields: readonly ["domesticStates"];
+        readonly affectedFields: readonly ["domesticState"];
     };
     readonly STATES_CONSECUTIVE_DUPLICATES_DETECTED: {
         readonly message: "There are two entries for {state} with timeframes that immediately follow each other. {state} ending {firstPeriodEnd}, and {state} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {state}. ";
         readonly params: readonly ["state", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
-        readonly affectedFields: readonly ["domesticStates"];
+        readonly affectedFields: readonly ["domesticState"];
     };
     readonly DOMESTIC_STATE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first state ({earliestState} starting {earliestStateStartDate}). There must be a state that begins on {dateEstablished}.";
         readonly params: readonly ["dateEstablished", "earliestState", "earliestStateStartDate"];
-        readonly affectedFields: readonly ["domesticStates", "dateEstablished"];
+        readonly affectedFields: readonly ["domesticState", "dateEstablished"];
     };
     readonly STATES_DATES_OVERLAP: {
         readonly message: "The client already has {state} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
         readonly params: readonly ["state", "startDate1", "endDate1", "startDate2", "endDate2"];
-        readonly affectedFields: readonly ["domesticStates"];
+        readonly affectedFields: readonly ["domesticState"];
     };
     readonly ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
         readonly message: "Only the last domestic state can be open without an end date. Add an ending date to the existing state before adding a start date for a new state.";

package/dist/validation/features/client-records-entity-states-histories.validation-messages.js

@@ -10,12 +10,12 @@ exports.CLIENT_RECORDS_ENTITY_STATES = {
     NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
         message: `The state, {domesticState}, starts on {domesticStateStartingDate}, which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the state or the client's date established.`,
         params: ['clientDateEstablished', 'domesticState', 'domesticStateStartingDate'],
-        affectedFields: ['dateEstablished', 'domesticStates'],
+        affectedFields: ['dateEstablished', 'domesticState'],
     },
     NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
         message: `One or more states have a start date which is after the client's close date of {clientCloseDate}. {domesticState} starting {domesticStateStartingDate}. Please update the state/s start date/s to be before the client's close date, or update the client's close date.`,
         params: ['clientCloseDate', 'domesticState', 'domesticStateStartingDate'],
-        affectedFields: ['closeDate', 'domesticStates'],
+        affectedFields: ['closeDate', 'domesticState'],
     },
     DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
         message: `Current Domestic State Starting Date cannot be Empty`,
@@ -33,7 +33,7 @@ exports.CLIENT_RECORDS_ENTITY_STATES = {
     },
     AT_LEAST_ONE_DOMESTIC_STATE_SHOULD_EXIST: {
         message: `At least one domestic state should exist`,
-        affectedFields: ['domesticStates'],
+        affectedFields: ['domesticState'],
     },
     STATES_STARTING_DATE_NOT_POPULATED: {
         message: `Starting date for {state} cannot be empty`,
@@ -58,22 +58,22 @@ exports.CLIENT_RECORDS_ENTITY_STATES = {
     DOMESTIC_STATES_DATE_GAP_DETECTED: {
         message: `There is a gap in the timeframes between {currentState}, ending {currentStateEndDate}, and {nextState}, starting {nextStateStartDate}. Please adjust the dates to fill this gap.`,
         params: ['currentState', 'currentStateEndDate', 'nextState', 'nextStateStartDate'],
-        affectedFields: ['domesticStates'],
+        affectedFields: ['domesticState'],
     },
     STATES_CONSECUTIVE_DUPLICATES_DETECTED: {
         message: `There are two entries for {state} with timeframes that immediately follow each other. {state} ending {firstPeriodEnd}, and {state} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {state}. `,
         params: ['state', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
-        affectedFields: ['domesticStates'],
+        affectedFields: ['domesticState'],
     },
     DOMESTIC_STATE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first state ({earliestState} starting {earliestStateStartDate}). There must be a state that begins on {dateEstablished}.`,
         params: ['dateEstablished', 'earliestState', 'earliestStateStartDate'],
-        affectedFields: ['domesticStates', 'dateEstablished'],
+        affectedFields: ['domesticState', 'dateEstablished'],
     },
     STATES_DATES_OVERLAP: {
         message: `The client already has {state} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
         params: ['state', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
-        affectedFields: ['domesticStates'],
+        affectedFields: ['domesticState'],
     },
     ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
         message: `Only the last domestic state can be open without an end date. Add an ending date to the existing state before adding a start date for a new state.`,

package/dist/validation/features/client-records-entity-types-histories.validation-messages.d.ts

@@ -7,12 +7,12 @@ export declare const CLIENT_RECORDS_ENTITY_TYPES: {
     readonly NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPE_STARTING_DATE: {
         readonly message: "One or more entity types have a start date that is before the client's date established, {clientDateEstablished}. ({entityType} starting {entityTypeStartingDate}). Please update the entity type start dates to be on or after the client's date established, or update the client's date established.";
         readonly params: readonly ["clientDateEstablished", "entityType", "entityTypeStartingDate"];
-        readonly affectedFields: readonly ["dateEstablished", "entityTypes"];
+        readonly affectedFields: readonly ["dateEstablished", "entityType"];
     };
     readonly NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPE_STARTING_DATE: {
         readonly message: "One or more entity types have start dates that are after the client's close date, {clientCloseDate}. {entityType} starting {entityTypeStartingDate}. Please update the entity type/s end date/s to be on or before the client's close date, or update the client's close date.";
         readonly params: readonly ["clientCloseDate", "entityType", "entityTypeStartingDate"];
-        readonly affectedFields: readonly ["closeDate", "entityTypes"];
+        readonly affectedFields: readonly ["closeDate", "entityType"];
     };
     readonly ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
         readonly message: "Current Entity Type Starting Date cannot be Empty";
@@ -29,7 +29,7 @@ export declare const CLIENT_RECORDS_ENTITY_TYPES: {
     };
     readonly AT_LEAST_ONE_ENTITY_TYPE_SHOULD_EXIST: {
         readonly message: "At least one entity type should exist";
-        readonly affectedFields: readonly ["entityTypes"];
+        readonly affectedFields: readonly ["entityType"];
     };
     readonly ENTITY_TYPES_STARTING_DATE_NOT_POPULATED: {
         readonly message: "Starting date for {entityType} cannot be empty";
@@ -54,22 +54,22 @@ export declare const CLIENT_RECORDS_ENTITY_TYPES: {
     readonly ENTITY_TYPES_DATE_GAP_DETECTED: {
         readonly message: "There is a gap in the timeframes between {currentEntityType}, ending {currentEntityTypeEndDate}, and {nextEntityType}, starting {nextEntityTypeStartDate}. Please adjust the dates to fill this gap.";
         readonly params: readonly ["currentEntityType", "currentEntityTypeEndDate", "nextEntityType", "nextEntityTypeStartDate"];
-        readonly affectedFields: readonly ["entityTypes"];
+        readonly affectedFields: readonly ["entityType"];
     };
     readonly ENTITY_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
         readonly message: "There are two entries for {entityType} with timeframes that immediately follow each other. {entityType} ending {firstPeriodEnd}, and {entityType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {entityType}. ";
         readonly params: readonly ["entityType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
-        readonly affectedFields: readonly ["entityTypes"];
+        readonly affectedFields: readonly ["entityType"];
     };
     readonly ENTITY_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first entity type ({earliestEntityType} starting {earliestEntityTypeStartDate}). There must be an entity type that begins on {dateEstablished}.";
         readonly params: readonly ["dateEstablished", "earliestEntityType", "earliestEntityTypeStartDate"];
-        readonly affectedFields: readonly ["entityTypes", "dateEstablished"];
+        readonly affectedFields: readonly ["entityType", "dateEstablished"];
     };
     readonly ENTITY_TYPES_DATES_OVERLAP: {
         readonly message: "The client already has {entityType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
         readonly params: readonly ["entityType", "startDate1", "endDate1", "startDate2", "endDate2"];
-        readonly affectedFields: readonly ["entityTypes"];
+        readonly affectedFields: readonly ["entityType"];
     };
     readonly ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
         readonly message: "Only the last entity type can be open without an end date. Add an ending date to the existing entity type before adding a start date for a new entity type.";

package/dist/validation/features/client-records-entity-types-histories.validation-messages.js

@@ -10,12 +10,12 @@ exports.CLIENT_RECORDS_ENTITY_TYPES = {
     NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPE_STARTING_DATE: {
         message: `One or more entity types have a start date that is before the client's date established, {clientDateEstablished}. ({entityType} starting {entityTypeStartingDate}). Please update the entity type start dates to be on or after the client's date established, or update the client's date established.`,
         params: ['clientDateEstablished', 'entityType', 'entityTypeStartingDate'],
-        affectedFields: ['dateEstablished', 'entityTypes'],
+        affectedFields: ['dateEstablished', 'entityType'],
     },
     NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPE_STARTING_DATE: {
         message: `One or more entity types have start dates that are after the client's close date, {clientCloseDate}. {entityType} starting {entityTypeStartingDate}. Please update the entity type/s end date/s to be on or before the client's close date, or update the client's close date.`,
         params: ['clientCloseDate', 'entityType', 'entityTypeStartingDate'],
-        affectedFields: ['closeDate', 'entityTypes'],
+        affectedFields: ['closeDate', 'entityType'],
     },
     ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
         message: `Current Entity Type Starting Date cannot be Empty`,
@@ -32,7 +32,7 @@ exports.CLIENT_RECORDS_ENTITY_TYPES = {
     },
     AT_LEAST_ONE_ENTITY_TYPE_SHOULD_EXIST: {
         message: `At least one entity type should exist`,
-        affectedFields: ['entityTypes'],
+        affectedFields: ['entityType'],
     },
     ENTITY_TYPES_STARTING_DATE_NOT_POPULATED: {
         message: `Starting date for {entityType} cannot be empty`,
@@ -57,22 +57,22 @@ exports.CLIENT_RECORDS_ENTITY_TYPES = {
     ENTITY_TYPES_DATE_GAP_DETECTED: {
         message: `There is a gap in the timeframes between {currentEntityType}, ending {currentEntityTypeEndDate}, and {nextEntityType}, starting {nextEntityTypeStartDate}. Please adjust the dates to fill this gap.`,
         params: ['currentEntityType', 'currentEntityTypeEndDate', 'nextEntityType', 'nextEntityTypeStartDate'],
-        affectedFields: ['entityTypes'],
+        affectedFields: ['entityType'],
     },
     ENTITY_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
         message: `There are two entries for {entityType} with timeframes that immediately follow each other. {entityType} ending {firstPeriodEnd}, and {entityType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {entityType}. `,
         params: ['entityType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
-        affectedFields: ['entityTypes'],
+        affectedFields: ['entityType'],
     },
     ENTITY_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first entity type ({earliestEntityType} starting {earliestEntityTypeStartDate}). There must be an entity type that begins on {dateEstablished}.`,
         params: ['dateEstablished', 'earliestEntityType', 'earliestEntityTypeStartDate'],
-        affectedFields: ['entityTypes', 'dateEstablished'],
+        affectedFields: ['entityType', 'dateEstablished'],
     },
     ENTITY_TYPES_DATES_OVERLAP: {
         message: `The client already has {entityType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
         params: ['entityType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
-        affectedFields: ['entityTypes'],
+        affectedFields: ['entityType'],
     },
     ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
         message: `Only the last entity type can be open without an end date. Add an ending date to the existing entity type before adding a start date for a new entity type.`,

package/dist/validation/features/client-records-filing-types-histories.validation-messages.d.ts

@@ -15,12 +15,12 @@ export declare const CLIENT_RECORDS_FILING_TYPES: {
     readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
         readonly message: "The Parent/Sub status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Parent/Sub status or the client's date established.";
         readonly params: readonly ["clientDateEstablished", "filingType", "filingTypeStartingDate"];
-        readonly affectedFields: readonly ["dateEstablished", "filingTypes"];
+        readonly affectedFields: readonly ["dateEstablished", "filingType"];
     };
     readonly NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
         readonly message: "One or more Parent/Sub status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.";
         readonly params: readonly ["clientCloseDate", "filingType", "filingTypeStartingDate"];
-        readonly affectedFields: readonly ["closeDate", "filingTypes"];
+        readonly affectedFields: readonly ["closeDate", "filingType"];
     };
     readonly FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
         readonly message: "Current Parent/Sub status Starting Date cannot be Empty";
@@ -37,7 +37,7 @@ export declare const CLIENT_RECORDS_FILING_TYPES: {
     };
     readonly AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
         readonly message: "At least one Parent/Sub status should exist";
-        readonly affectedFields: readonly ["filingTypes"];
+        readonly affectedFields: readonly ["filingType"];
     };
     readonly FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
         readonly message: "Starting date for {filingType} cannot be empty";
@@ -62,22 +62,22 @@ export declare const CLIENT_RECORDS_FILING_TYPES: {
     readonly FILING_TYPES_DATE_GAP_DETECTED: {
         readonly message: "There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.";
         readonly params: readonly ["currentFilingType", "currentFilingTypeEndDate", "nextFilingType", "nextFilingTypeStartDate"];
-        readonly affectedFields: readonly ["filingTypes"];
+        readonly affectedFields: readonly ["filingType"];
     };
     readonly FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
         readonly message: "There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. ";
         readonly params: readonly ["filingType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
-        readonly affectedFields: readonly ["filingTypes"];
+        readonly affectedFields: readonly ["filingType"];
     };
     readonly FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first Parent/Sub status ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a Parent/Sub status that begins on {dateEstablished}.";
         readonly params: readonly ["dateEstablished", "earliestFilingType", "earliestFilingTypeStartDate"];
-        readonly affectedFields: readonly ["filingTypes", "dateEstablished"];
+        readonly affectedFields: readonly ["filingType", "dateEstablished"];
     };
     readonly FILING_TYPES_DATES_OVERLAP: {
         readonly message: "The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
         readonly params: readonly ["filingType", "startDate1", "endDate1", "startDate2", "endDate2"];
-        readonly affectedFields: readonly ["filingTypes"];
+        readonly affectedFields: readonly ["filingType"];
     };
     readonly ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
         readonly message: "Only the last Parent/Sub status can be open without an end date. Add an ending date to the existing Parent/Sub status before adding a start date for a new Parent/Sub status.";

package/dist/validation/features/client-records-filing-types-histories.validation-messages.js

@@ -18,12 +18,12 @@ exports.CLIENT_RECORDS_FILING_TYPES = {
     NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
         message: `The Parent/Sub status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Parent/Sub status or the client's date established.`,
         params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
-        affectedFields: ['dateEstablished', 'filingTypes'],
+        affectedFields: ['dateEstablished', 'filingType'],
     },
     NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
         message: `One or more Parent/Sub status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
         params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
-        affectedFields: ['closeDate', 'filingTypes'],
+        affectedFields: ['closeDate', 'filingType'],
     },
     FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
         message: `Current Parent/Sub status Starting Date cannot be Empty`,
@@ -40,7 +40,7 @@ exports.CLIENT_RECORDS_FILING_TYPES = {
     },
     AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
         message: `At least one Parent/Sub status should exist`,
-        affectedFields: ['filingTypes'],
+        affectedFields: ['filingType'],
     },
     FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
         message: `Starting date for {filingType} cannot be empty`,
@@ -65,22 +65,22 @@ exports.CLIENT_RECORDS_FILING_TYPES = {
     FILING_TYPES_DATE_GAP_DETECTED: {
         message: `There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.`,
         params: ['currentFilingType', 'currentFilingTypeEndDate', 'nextFilingType', 'nextFilingTypeStartDate'],
-        affectedFields: ['filingTypes'],
+        affectedFields: ['filingType'],
     },
     FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
         message: `There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. `,
         params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
-        affectedFields: ['filingTypes'],
+        affectedFields: ['filingType'],
     },
     FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
         message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first Parent/Sub status ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a Parent/Sub status that begins on {dateEstablished}.`,
         params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
-        affectedFields: ['filingTypes', 'dateEstablished'],
+        affectedFields: ['filingType', 'dateEstablished'],
     },
     FILING_TYPES_DATES_OVERLAP: {
         message: `The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
         params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
-        affectedFields: ['filingTypes'],
+        affectedFields: ['filingType'],
     },
     ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
         message: `Only the last Parent/Sub status can be open without an end date. Add an ending date to the existing Parent/Sub status before adding a start date for a new Parent/Sub status.`,

package/dist/validation/validation-messages.d.ts

@@ -360,12 +360,12 @@ export declare const VALIDATION_MESSAGES: {
         readonly NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPE_STARTING_DATE: {
             readonly message: "One or more entity types have a start date that is before the client's date established, {clientDateEstablished}. ({entityType} starting {entityTypeStartingDate}). Please update the entity type start dates to be on or after the client's date established, or update the client's date established.";
             readonly params: readonly ["clientDateEstablished", "entityType", "entityTypeStartingDate"];
-            readonly affectedFields: readonly ["dateEstablished", "entityTypes"];
+            readonly affectedFields: readonly ["dateEstablished", "entityType"];
         };
         readonly NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPE_STARTING_DATE: {
             readonly message: "One or more entity types have start dates that are after the client's close date, {clientCloseDate}. {entityType} starting {entityTypeStartingDate}. Please update the entity type/s end date/s to be on or before the client's close date, or update the client's close date.";
             readonly params: readonly ["clientCloseDate", "entityType", "entityTypeStartingDate"];
-            readonly affectedFields: readonly ["closeDate", "entityTypes"];
+            readonly affectedFields: readonly ["closeDate", "entityType"];
         };
         readonly ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
             readonly message: "Current Entity Type Starting Date cannot be Empty";
@@ -382,7 +382,7 @@ export declare const VALIDATION_MESSAGES: {
         };
         readonly AT_LEAST_ONE_ENTITY_TYPE_SHOULD_EXIST: {
             readonly message: "At least one entity type should exist";
-            readonly affectedFields: readonly ["entityTypes"];
+            readonly affectedFields: readonly ["entityType"];
         };
         readonly ENTITY_TYPES_STARTING_DATE_NOT_POPULATED: {
             readonly message: "Starting date for {entityType} cannot be empty";
@@ -407,22 +407,22 @@ export declare const VALIDATION_MESSAGES: {
         readonly ENTITY_TYPES_DATE_GAP_DETECTED: {
             readonly message: "There is a gap in the timeframes between {currentEntityType}, ending {currentEntityTypeEndDate}, and {nextEntityType}, starting {nextEntityTypeStartDate}. Please adjust the dates to fill this gap.";
             readonly params: readonly ["currentEntityType", "currentEntityTypeEndDate", "nextEntityType", "nextEntityTypeStartDate"];
-            readonly affectedFields: readonly ["entityTypes"];
+            readonly affectedFields: readonly ["entityType"];
         };
         readonly ENTITY_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
             readonly message: "There are two entries for {entityType} with timeframes that immediately follow each other. {entityType} ending {firstPeriodEnd}, and {entityType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {entityType}. ";
             readonly params: readonly ["entityType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
-            readonly affectedFields: readonly ["entityTypes"];
+            readonly affectedFields: readonly ["entityType"];
         };
         readonly ENTITY_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
             readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first entity type ({earliestEntityType} starting {earliestEntityTypeStartDate}). There must be an entity type that begins on {dateEstablished}.";
             readonly params: readonly ["dateEstablished", "earliestEntityType", "earliestEntityTypeStartDate"];
-            readonly affectedFields: readonly ["entityTypes", "dateEstablished"];
+            readonly affectedFields: readonly ["entityType", "dateEstablished"];
         };
         readonly ENTITY_TYPES_DATES_OVERLAP: {
             readonly message: "The client already has {entityType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
             readonly params: readonly ["entityType", "startDate1", "endDate1", "startDate2", "endDate2"];
-            readonly affectedFields: readonly ["entityTypes"];
+            readonly affectedFields: readonly ["entityType"];
         };
         readonly ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
             readonly message: "Only the last entity type can be open without an end date. Add an ending date to the existing entity type before adding a start date for a new entity type.";
@@ -450,12 +450,12 @@ export declare const VALIDATION_MESSAGES: {
         readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
             readonly message: "The Parent/Sub status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Parent/Sub status or the client's date established.";
             readonly params: readonly ["clientDateEstablished", "filingType", "filingTypeStartingDate"];
-            readonly affectedFields: readonly ["dateEstablished", "filingTypes"];
+            readonly affectedFields: readonly ["dateEstablished", "filingType"];
         };
         readonly NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
             readonly message: "One or more Parent/Sub status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.";
             readonly params: readonly ["clientCloseDate", "filingType", "filingTypeStartingDate"];
-            readonly affectedFields: readonly ["closeDate", "filingTypes"];
+            readonly affectedFields: readonly ["closeDate", "filingType"];
         };
         readonly FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
             readonly message: "Current Parent/Sub status Starting Date cannot be Empty";
@@ -472,7 +472,7 @@ export declare const VALIDATION_MESSAGES: {
         };
         readonly AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
             readonly message: "At least one Parent/Sub status should exist";
-            readonly affectedFields: readonly ["filingTypes"];
+            readonly affectedFields: readonly ["filingType"];
         };
         readonly FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
             readonly message: "Starting date for {filingType} cannot be empty";
@@ -497,22 +497,22 @@ export declare const VALIDATION_MESSAGES: {
         readonly FILING_TYPES_DATE_GAP_DETECTED: {
             readonly message: "There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.";
             readonly params: readonly ["currentFilingType", "currentFilingTypeEndDate", "nextFilingType", "nextFilingTypeStartDate"];
-            readonly affectedFields: readonly ["filingTypes"];
+            readonly affectedFields: readonly ["filingType"];
         };
         readonly FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
             readonly message: "There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. ";
             readonly params: readonly ["filingType", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
-            readonly affectedFields: readonly ["filingTypes"];
+            readonly affectedFields: readonly ["filingType"];
         };
         readonly FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
             readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first Parent/Sub status ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a Parent/Sub status that begins on {dateEstablished}.";
             readonly params: readonly ["dateEstablished", "earliestFilingType", "earliestFilingTypeStartDate"];
-            readonly affectedFields: readonly ["filingTypes", "dateEstablished"];
+            readonly affectedFields: readonly ["filingType", "dateEstablished"];
         };
         readonly FILING_TYPES_DATES_OVERLAP: {
             readonly message: "The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
             readonly params: readonly ["filingType", "startDate1", "endDate1", "startDate2", "endDate2"];
-            readonly affectedFields: readonly ["filingTypes"];
+            readonly affectedFields: readonly ["filingType"];
         };
         readonly ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
             readonly message: "Only the last Parent/Sub status can be open without an end date. Add an ending date to the existing Parent/Sub status before adding a start date for a new Parent/Sub status.";
@@ -532,12 +532,12 @@ export declare const VALIDATION_MESSAGES: {
         readonly NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
             readonly message: "The state, {domesticState}, starts on {domesticStateStartingDate}, which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the state or the client's date established.";
             readonly params: readonly ["clientDateEstablished", "domesticState", "domesticStateStartingDate"];
-            readonly affectedFields: readonly ["dateEstablished", "domesticStates"];
+            readonly affectedFields: readonly ["dateEstablished", "domesticState"];
         };
         readonly NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
             readonly message: "One or more states have a start date which is after the client's close date of {clientCloseDate}. {domesticState} starting {domesticStateStartingDate}. Please update the state/s start date/s to be before the client's close date, or update the client's close date.";
             readonly params: readonly ["clientCloseDate", "domesticState", "domesticStateStartingDate"];
-            readonly affectedFields: readonly ["closeDate", "domesticStates"];
+            readonly affectedFields: readonly ["closeDate", "domesticState"];
         };
         readonly DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
             readonly message: "Current Domestic State Starting Date cannot be Empty";
@@ -555,7 +555,7 @@ export declare const VALIDATION_MESSAGES: {
         };
         readonly AT_LEAST_ONE_DOMESTIC_STATE_SHOULD_EXIST: {
             readonly message: "At least one domestic state should exist";
-            readonly affectedFields: readonly ["domesticStates"];
+            readonly affectedFields: readonly ["domesticState"];
         };
         readonly STATES_STARTING_DATE_NOT_POPULATED: {
             readonly message: "Starting date for {state} cannot be empty";
@@ -580,22 +580,22 @@ export declare const VALIDATION_MESSAGES: {
         readonly DOMESTIC_STATES_DATE_GAP_DETECTED: {
             readonly message: "There is a gap in the timeframes between {currentState}, ending {currentStateEndDate}, and {nextState}, starting {nextStateStartDate}. Please adjust the dates to fill this gap.";
             readonly params: readonly ["currentState", "currentStateEndDate", "nextState", "nextStateStartDate"];
-            readonly affectedFields: readonly ["domesticStates"];
+            readonly affectedFields: readonly ["domesticState"];
         };
         readonly STATES_CONSECUTIVE_DUPLICATES_DETECTED: {
             readonly message: "There are two entries for {state} with timeframes that immediately follow each other. {state} ending {firstPeriodEnd}, and {state} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {state}. ";
             readonly params: readonly ["state", "firstPeriodStart", "firstPeriodEnd", "secondPeriodStart"];
-            readonly affectedFields: readonly ["domesticStates"];
+            readonly affectedFields: readonly ["domesticState"];
         };
         readonly DOMESTIC_STATE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
             readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start of its first state ({earliestState} starting {earliestStateStartDate}). There must be a state that begins on {dateEstablished}.";
             readonly params: readonly ["dateEstablished", "earliestState", "earliestStateStartDate"];
-            readonly affectedFields: readonly ["domesticStates", "dateEstablished"];
+            readonly affectedFields: readonly ["domesticState", "dateEstablished"];
         };
         readonly STATES_DATES_OVERLAP: {
             readonly message: "The client already has {state} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.";
             readonly params: readonly ["state", "startDate1", "endDate1", "startDate2", "endDate2"];
-            readonly affectedFields: readonly ["domesticStates"];
+            readonly affectedFields: readonly ["domesticState"];
         };
         readonly ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
             readonly message: "Only the last domestic state can be open without an end date. Add an ending date to the existing state before adding a start date for a new state.";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forwardslashns/taskit-validation-messages",
-  "version": "1.3.6",
+  "version": "1.3.7",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "commonjs",

package/src/validation/features/client-records-entity-states-histories.validation-messages.ts

@@ -7,12 +7,12 @@ export const CLIENT_RECORDS_ENTITY_STATES = {
   NOT_ALIGNED_DATE_ESTABLISHED_DOMESTIC_STATE_STARTING_DATE: {
     message: `The state, {domesticState}, starts on {domesticStateStartingDate}, which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the state or the client's date established.`,
     params: ['clientDateEstablished', 'domesticState', 'domesticStateStartingDate'],
-    affectedFields: ['dateEstablished', 'domesticStates'],
+    affectedFields: ['dateEstablished', 'domesticState'],
   },
   NOT_ALIGNED_CLOSE_DATE_DOMESTIC_STATE_STARTING_DATE: {
     message: `One or more states have a start date which is after the client's close date of {clientCloseDate}. {domesticState} starting {domesticStateStartingDate}. Please update the state/s start date/s to be before the client's close date, or update the client's close date.`,
     params: ['clientCloseDate', 'domesticState', 'domesticStateStartingDate'],
-    affectedFields: ['closeDate', 'domesticStates'],
+    affectedFields: ['closeDate', 'domesticState'],
   },
   DOMESTIC_STATE_STARTING_DATE_NOT_POPULATED: {
     message: `Current Domestic State Starting Date cannot be Empty`,
@@ -30,7 +30,7 @@ export const CLIENT_RECORDS_ENTITY_STATES = {
   },
   AT_LEAST_ONE_DOMESTIC_STATE_SHOULD_EXIST: {
     message: `At least one domestic state should exist`,
-    affectedFields: ['domesticStates'],
+    affectedFields: ['domesticState'],
   },
   STATES_STARTING_DATE_NOT_POPULATED: {
     message: `Starting date for {state} cannot be empty`,
@@ -55,22 +55,22 @@ export const CLIENT_RECORDS_ENTITY_STATES = {
   DOMESTIC_STATES_DATE_GAP_DETECTED: {
     message: `There is a gap in the timeframes between {currentState}, ending {currentStateEndDate}, and {nextState}, starting {nextStateStartDate}. Please adjust the dates to fill this gap.`,
     params: ['currentState', 'currentStateEndDate', 'nextState', 'nextStateStartDate'],
-    affectedFields: ['domesticStates'],
+    affectedFields: ['domesticState'],
   },
   STATES_CONSECUTIVE_DUPLICATES_DETECTED: {
     message: `There are two entries for {state} with timeframes that immediately follow each other. {state} ending {firstPeriodEnd}, and {state} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {state}. `,
     params: ['state', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
-    affectedFields: ['domesticStates'],
+    affectedFields: ['domesticState'],
   },
   DOMESTIC_STATE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
     message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first state ({earliestState} starting {earliestStateStartDate}). There must be a state that begins on {dateEstablished}.`,
     params: ['dateEstablished', 'earliestState', 'earliestStateStartDate'],
-    affectedFields: ['domesticStates', 'dateEstablished'],
+    affectedFields: ['domesticState', 'dateEstablished'],
   },
   STATES_DATES_OVERLAP: {
     message: `The client already has {state} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
     params: ['state', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
-    affectedFields: ['domesticStates'],
+    affectedFields: ['domesticState'],
   },
   ALL_NON_LAST_DOMESTIC_STATES_REQUIRE_ENDING_DATE: {
     message: `Only the last domestic state can be open without an end date. Add an ending date to the existing state before adding a start date for a new state.`,

package/src/validation/features/client-records-entity-types-histories.validation-messages.ts

@@ -7,12 +7,12 @@ export const CLIENT_RECORDS_ENTITY_TYPES = {
   NOT_ALIGNED_DATE_ESTABLISHED_ENTITY_TYPE_STARTING_DATE: {
     message: `One or more entity types have a start date that is before the client's date established, {clientDateEstablished}. ({entityType} starting {entityTypeStartingDate}). Please update the entity type start dates to be on or after the client's date established, or update the client's date established.`,
     params: ['clientDateEstablished', 'entityType', 'entityTypeStartingDate'],
-    affectedFields: ['dateEstablished', 'entityTypes'],
+    affectedFields: ['dateEstablished', 'entityType'],
   },
   NOT_ALIGNED_CLOSE_DATE_ENTITY_TYPE_STARTING_DATE: {
     message: `One or more entity types have start dates that are after the client's close date, {clientCloseDate}. {entityType} starting {entityTypeStartingDate}. Please update the entity type/s end date/s to be on or before the client's close date, or update the client's close date.`,
     params: ['clientCloseDate', 'entityType', 'entityTypeStartingDate'],
-    affectedFields: ['closeDate', 'entityTypes'],
+    affectedFields: ['closeDate', 'entityType'],
   },
   ENTITY_TYPE_STARTING_DATE_NOT_POPULATED: {
     message: `Current Entity Type Starting Date cannot be Empty`,
@@ -29,7 +29,7 @@ export const CLIENT_RECORDS_ENTITY_TYPES = {
   },
   AT_LEAST_ONE_ENTITY_TYPE_SHOULD_EXIST: {
     message: `At least one entity type should exist`,
-    affectedFields: ['entityTypes'],
+    affectedFields: ['entityType'],
   },
   ENTITY_TYPES_STARTING_DATE_NOT_POPULATED: {
     message: `Starting date for {entityType} cannot be empty`,
@@ -54,22 +54,22 @@ export const CLIENT_RECORDS_ENTITY_TYPES = {
   ENTITY_TYPES_DATE_GAP_DETECTED: {
     message: `There is a gap in the timeframes between {currentEntityType}, ending {currentEntityTypeEndDate}, and {nextEntityType}, starting {nextEntityTypeStartDate}. Please adjust the dates to fill this gap.`,
     params: ['currentEntityType', 'currentEntityTypeEndDate', 'nextEntityType', 'nextEntityTypeStartDate'],
-    affectedFields: ['entityTypes'],
+    affectedFields: ['entityType'],
   },
   ENTITY_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
     message: `There are two entries for {entityType} with timeframes that immediately follow each other. {entityType} ending {firstPeriodEnd}, and {entityType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {entityType}. `,
     params: ['entityType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
-    affectedFields: ['entityTypes'],
+    affectedFields: ['entityType'],
   },
   ENTITY_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
     message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first entity type ({earliestEntityType} starting {earliestEntityTypeStartDate}). There must be an entity type that begins on {dateEstablished}.`,
     params: ['dateEstablished', 'earliestEntityType', 'earliestEntityTypeStartDate'],
-    affectedFields: ['entityTypes', 'dateEstablished'],
+    affectedFields: ['entityType', 'dateEstablished'],
   },
   ENTITY_TYPES_DATES_OVERLAP: {
     message: `The client already has {entityType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
     params: ['entityType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
-    affectedFields: ['entityTypes'],
+    affectedFields: ['entityType'],
   },
   ALL_NON_LAST_ENTITY_TYPES_REQUIRE_ENDING_DATE: {
     message: `Only the last entity type can be open without an end date. Add an ending date to the existing entity type before adding a start date for a new entity type.`,

package/src/validation/features/client-records-filing-types-histories.validation-messages.ts

@@ -15,12 +15,12 @@ export const CLIENT_RECORDS_FILING_TYPES = {
   NOT_ALIGNED_DATE_ESTABLISHED_FILING_TYPE_STARTING_DATE: {
     message: `The Parent/Sub status {filingType} starts on {filingTypeStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Parent/Sub status or the client's date established.`,
     params: ['clientDateEstablished', 'filingType', 'filingTypeStartingDate'],
-    affectedFields: ['dateEstablished', 'filingTypes'],
+    affectedFields: ['dateEstablished', 'filingType'],
   },
   NOT_ALIGNED_CLOSE_DATE_FILING_TYPE_STARTING_DATE: {
     message: `One or more Parent/Sub status have a start date which is after the client's close date of {clientCloseDate}. {filingType}, starting {filingTypeStartingDate}. Please update the start date to be earlier than the client's close date, or update the client's close date.`,
     params: ['clientCloseDate', 'filingType', 'filingTypeStartingDate'],
-    affectedFields: ['closeDate', 'filingTypes'],
+    affectedFields: ['closeDate', 'filingType'],
   },
   FILING_TYPE_STARTING_DATE_NOT_POPULATED: {
     message: `Current Parent/Sub status Starting Date cannot be Empty`,
@@ -37,7 +37,7 @@ export const CLIENT_RECORDS_FILING_TYPES = {
   },
   AT_LEAST_ONE_FILING_TYPE_SHOULD_EXIST: {
     message: `At least one Parent/Sub status should exist`,
-    affectedFields: ['filingTypes'],
+    affectedFields: ['filingType'],
   },
   FILING_TYPES_STARTING_DATE_NOT_POPULATED: {
     message: `Starting date for {filingType} cannot be empty`,
@@ -62,22 +62,22 @@ export const CLIENT_RECORDS_FILING_TYPES = {
   FILING_TYPES_DATE_GAP_DETECTED: {
     message: `There is a gap in the timeframes between {currentFilingType}, ending {currentFilingTypeEndDate}, and {nextFilingType}, starting {nextFilingTypeStartDate}. Please adjust the dates to fill this gap.`,
     params: ['currentFilingType', 'currentFilingTypeEndDate', 'nextFilingType', 'nextFilingTypeStartDate'],
-    affectedFields: ['filingTypes'],
+    affectedFields: ['filingType'],
   },
   FILING_TYPES_CONSECUTIVE_DUPLICATES_DETECTED: {
     message: `There are two entries for {filingType} with timeframes that immediately follow each other. {filingType} ending {firstPeriodEnd}, and {filingType} starting {secondPeriodStart}. Please update one entry to include the entire timeframe for {filingType}. `,
     params: ['filingType', 'firstPeriodStart', 'firstPeriodEnd', 'secondPeriodStart'],
-    affectedFields: ['filingTypes'],
+    affectedFields: ['filingType'],
   },
   FILING_TYPE_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
     message: `There is a gap between the client's date established ({dateEstablished}) and the start of its first Parent/Sub status ({earliestFilingType} starting {earliestFilingTypeStartDate}). There must be a Parent/Sub status that begins on {dateEstablished}.`,
     params: ['dateEstablished', 'earliestFilingType', 'earliestFilingTypeStartDate'],
-    affectedFields: ['filingTypes', 'dateEstablished'],
+    affectedFields: ['filingType', 'dateEstablished'],
   },
   FILING_TYPES_DATES_OVERLAP: {
     message: `The client already has {filingType} starting from {startDate2} to {endDate2}. Your current entity type overlaps with that time. Please adjust the dates so they don't overlap.`,
     params: ['filingType', 'startDate1', 'endDate1', 'startDate2', 'endDate2'],
-    affectedFields: ['filingTypes'],
+    affectedFields: ['filingType'],
   },
   ALL_NON_LAST_FILING_TYPES_REQUIRE_ENDING_DATE: {
     message: `Only the last Parent/Sub status can be open without an end date. Add an ending date to the existing Parent/Sub status before adding a start date for a new Parent/Sub status.`,