@forwardslashns/taskit-validation-messages 1.10.7 → 1.10.9

package/dist/validation/features/account-categories.validation-messages.d.ts

@@ -11,7 +11,7 @@ export declare const ACCOUNT_CATEGORIES: {
     readonly NAME_ALREADY_EXISTS: {
         readonly message: "Account category with the same name '{name}' already exists";
         readonly params: readonly ["name"];
-        readonly affectedFields: readonly ["name"];
+        readonly affectedFields: readonly ["accountCategory"];
     };
     readonly OPTION_IN_USE: {
         readonly message: "This option is currently in use and cannot be deleted.";

package/dist/validation/features/account-categories.validation-messages.js

@@ -14,7 +14,7 @@ exports.ACCOUNT_CATEGORIES = {
     NAME_ALREADY_EXISTS: {
         message: `Account category with the same name '{name}' already exists`,
         params: ['name'],
-        affectedFields: ['name'],
+        affectedFields: ['accountCategory'],
     },
     OPTION_IN_USE: {
         message: `This option is currently in use and cannot be deleted.`,

package/dist/validation/features/account-ids.validation-messages.d.ts

@@ -11,12 +11,12 @@ export declare const ACCOUNT_IDS: {
     readonly NAME_ALREADY_EXISTS: {
         readonly message: "Account id with the same name '{name}' already exists";
         readonly params: readonly ["name"];
-        readonly affectedFields: readonly ["name"];
+        readonly affectedFields: readonly ["accountId"];
     };
     readonly ACCOUNT_CATEGORY_ID_DOES_NOT_EXIST: {
         readonly message: "Account category does not exist";
         readonly params: readonly ["id"];
-        readonly affectedFields: readonly ["accountCategoryId"];
+        readonly affectedFields: readonly ["accountCategory"];
     };
     readonly OPTION_IN_USE: {
         readonly message: "This option is currently in use and cannot be deleted.";

package/dist/validation/features/account-ids.validation-messages.js

@@ -14,12 +14,12 @@ exports.ACCOUNT_IDS = {
     NAME_ALREADY_EXISTS: {
         message: `Account id with the same name '{name}' already exists`,
         params: ['name'],
-        affectedFields: ['name'],
+        affectedFields: ['accountId'],
     },
     ACCOUNT_CATEGORY_ID_DOES_NOT_EXIST: {
         message: `Account category does not exist`,
         params: ['id'],
-        affectedFields: ['accountCategoryId'],
+        affectedFields: ['accountCategory'],
     },
     OPTION_IN_USE: {
         message: `This option is currently in use and cannot be deleted.`,

package/dist/validation/features/business-activities.validation-messages.d.ts

@@ -11,7 +11,7 @@ export declare const BUSINESS_ACTIVITIES: {
     readonly NAME_ALREADY_EXISTS: {
         readonly message: "Business activity with the same name '{name}' already exists.";
         readonly params: readonly ["name"];
-        readonly affectedFields: readonly ["name"];
+        readonly affectedFields: readonly ["bussinesActivity"];
     };
     readonly OPTION_IN_USE: {
         readonly message: "This option is currently in use and cannot be deleted.";

package/dist/validation/features/business-activities.validation-messages.js

@@ -14,7 +14,7 @@ exports.BUSINESS_ACTIVITIES = {
     NAME_ALREADY_EXISTS: {
         message: `Business activity with the same name '{name}' already exists.`,
         params: ['name'],
-        affectedFields: ['name'],
+        affectedFields: ['bussinesActivity'],
     },
     OPTION_IN_USE: {
         message: `This option is currently in use and cannot be deleted.`,

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

@@ -4,14 +4,6 @@ export declare const CLIENT_RECORDS_FILING_STATUSES: {
         readonly params: readonly ["id"];
         readonly affectedFields: readonly ["filingStatus"];
     };
-    readonly FILING_STATUS_PARENT_REQUIRED: {
-        readonly message: "Parent needs to be specified for filing status 'Files under parent'";
-        readonly affectedFields: readonly ["currentParent"];
-    };
-    readonly CURRENT_FILING_STATUS_PARENT_REQUIRED: {
-        readonly message: "Parent needs to be specified for current filing status 'Files under parent'";
-        readonly affectedFields: readonly ["currentParent"];
-    };
     readonly NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
         readonly message: "The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.";
         readonly params: readonly ["clientDateEstablished", "filingStatus", "filingStatusStartingDate"];
@@ -70,8 +62,8 @@ export declare const CLIENT_RECORDS_FILING_STATUSES: {
         readonly affectedFields: readonly ["filingStatus"];
     };
     readonly FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
-        readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start date of {earliestFilingStatus} ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.";
-        readonly params: readonly ["dateEstablished", "earliestFilingStatus", "earliestFilingStatusStartDate"];
+        readonly message: "There is a gap between the client's date established ({dateEstablished}) and the start date of the first Sub/Parent status ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.";
+        readonly params: readonly ["dateEstablished", "earliestFilingStatusStartDate"];
         readonly affectedFields: readonly ["filingStatus", "dateEstablished"];
     };
     readonly FILING_STATUSES_DATES_OVERLAP: {

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

@@ -1 +1 @@
-{"version":3,"file":"client-records-filing-statuses-histories.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-records-filing-statuses-histories.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyFjC,CAAC"}
+{"version":3,"file":"client-records-filing-statuses-histories.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-records-filing-statuses-histories.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,8BAA8B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiFjC,CAAC"}

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

@@ -7,14 +7,6 @@ exports.CLIENT_RECORDS_FILING_STATUSES = {
         params: ['id'],
         affectedFields: ['filingStatus'],
     },
-    FILING_STATUS_PARENT_REQUIRED: {
-        message: `Parent needs to be specified for filing status 'Files under parent'`,
-        affectedFields: ['currentParent'],
-    },
-    CURRENT_FILING_STATUS_PARENT_REQUIRED: {
-        message: `Parent needs to be specified for current filing status 'Files under parent'`,
-        affectedFields: ['currentParent'],
-    },
     NOT_ALIGNED_DATE_ESTABLISHED_FILING_STATUS_STARTING_DATE: {
         message: `The Sub/Parent status {filingStatus} starts on {filingStatusStartingDate} which is earlier than the client's date established, {clientDateEstablished}. Please adjust the start date of the Sub/Parent status or the client's date established.`,
         params: ['clientDateEstablished', 'filingStatus', 'filingStatusStartingDate'],
@@ -73,8 +65,8 @@ exports.CLIENT_RECORDS_FILING_STATUSES = {
         affectedFields: ['filingStatus'],
     },
     FILING_STATUS_EARLIEST_AND_DATE_ESTABLISHED_GAP_DETECTED: {
-        message: `There is a gap between the client's date established ({dateEstablished}) and the start date of {earliestFilingStatus} ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.`,
-        params: ['dateEstablished', 'earliestFilingStatus', 'earliestFilingStatusStartDate'],
+        message: `There is a gap between the client's date established ({dateEstablished}) and the start date of the first Sub/Parent status ({earliestFilingStatusStartDate}). Please ensure that the status of one Sub/Parent status matches the client's date established.`,
+        params: ['dateEstablished', 'earliestFilingStatusStartDate'],
         affectedFields: ['filingStatus', 'dateEstablished'],
     },
     FILING_STATUSES_DATES_OVERLAP: {

package/dist/validation/features/client-relationships-common.validation-messages.d.ts

@@ -1,12 +1,12 @@
 export declare const CLIENT_RELATIONSHIPS_COMMON: {
     readonly CURRENT_CLIENT_CANNOT_BE_RELATED_TO_CURRENT_CLIENT: {
         readonly message: "A client cannot have a relationship with itself.";
-        readonly affectedFields: readonly ["relatedClientId"];
+        readonly affectedFields: readonly ["relatedClient"];
     };
     readonly INVALID_RELATIONSHIP_TYPE_FOR_ENTITY_TYPE: {
         readonly message: "{clientName} is a/an {entityType}, which can't have {relationshipType}s. Please update the relationship type.";
         readonly params: readonly ["clientName", "entityType", "relationshipType"];
-        readonly affectedFields: readonly ["relationshipTypeId"];
+        readonly affectedFields: readonly ["relationshipType"];
     };
     readonly STARTING_DATE_BEFORE_CLIENT_DATE_ESTABLISHED: {
         readonly message: "This relationship's start date cannot be before {clientName}'s date established, {clientDateEstablished}. Please adjust the dates to proceed.";
@@ -34,32 +34,34 @@ export declare const CLIENT_RELATIONSHIPS_COMMON: {
         readonly affectedFields: readonly ["endingDate"];
     };
     readonly ENDING_DATE_AFTER_CLIENT_CLOSE_DATE: {
-        readonly message: "Please update the relationship ending date to be on or before the client's close date, {clientCloseDate}.";
-        readonly params: readonly ["clientCloseDate"];
+        readonly message: "{clientName}'s close date is {clientCloseDate}. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before {clientCloseDate}: {relationshipsWithEndingDateAfterCloseDate}, or update {clientName}'s close date.";
+        readonly params: readonly ["clientName", "clientCloseDate", "relationshipsWithEndingDateAfterCloseDate"];
         readonly affectedFields: readonly ["endingDate"];
     };
     readonly ENDING_DATE_AFTER_RELATED_CLIENT_CLOSE_DATE: {
-        readonly message: "Please update the relationship ending date to be on or before {relatedClientName}'s close date, {relatedClientCloseDate}.";
-        readonly params: readonly ["relatedClientName", "relatedClientCloseDate"];
+        readonly message: "{relatedClientName}'s close date is {relatedClientCloseDate}. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before {relatedClientCloseDate}: {relationshipsWithEndingDateAfterCloseDate}, or update {relatedClientName}'s close date.";
+        readonly params: readonly ["relatedClientName", "relatedClientCloseDate", "relationshipsWithEndingDateAfterCloseDate"];
         readonly affectedFields: readonly ["endingDate"];
     };
     readonly FINAL_REQUIRED_WHEN_ENDING_DATE_MATCHES_CLIENT_CLOSE_DATE: {
-        readonly message: "The client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.";
-        readonly affectedFields: readonly ["final"];
+        readonly message: "The relationship between {clientName} and {relatedClientName} has no end date or is not marked as final. Please update {relatedClientName}'s end date to be on or before {clientName}'s close date of {clientCloseDate}, or mark the relationship as final.";
+        readonly params: readonly ["clientName", "relatedClientName", "clientCloseDate"];
+        readonly affectedFields: readonly ["endingDate", "final"];
     };
     readonly FINAL_REQUIRED_WHEN_ENDING_DATE_MATCHES_RELATED_CLIENT_CLOSE_DATE: {
-        readonly message: "The related client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.";
-        readonly affectedFields: readonly ["final"];
+        readonly message: "The relationship between {clientName} and {relatedClientName} has no end date or is not marked as final. Please update {clientName}'s end date to be on or before {relatedClientName}'s close date of {relatedClientCloseDate}, or mark the relationship as final.";
+        readonly params: readonly ["clientName", "relatedClientName", "relatedClientCloseDate"];
+        readonly affectedFields: readonly ["endingDate", "final"];
     };
     readonly CIRCULAR_RELATIONSHIP_DETECTED: {
         readonly message: "{clientName} is listed as a {relationshipType} of {relatedClientName}, during the same timeframe that {relatedClientName} is listed as a {relationshipType} of {clientName}. Please review the relationship records for both clients and adjust the dates or relationship types to prevent a circular loop.";
         readonly params: readonly ["clientName", "relatedClientName", "relationshipType"];
-        readonly affectedFields: readonly ["relationshipTypeId", "relatedClientId", "startingDate", "endingDate"];
+        readonly affectedFields: readonly ["relationshipType", "relatedClient", "startingDate", "endingDate"];
     };
     readonly CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
         readonly message: "{relatedClientName} cannot be associated with {clientName} more than once within the same timeframe. Please ensure there are no conflicting relationships for these clients in this timeframe.";
         readonly params: readonly ["relatedClientName", "clientName"];
-        readonly affectedFields: readonly ["relationshipTypeId", "relatedClientId", "startingDate", "endingDate"];
+        readonly affectedFields: readonly ["relationshipType", "relatedClient", "startingDate", "endingDate"];
     };
     readonly CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
         readonly message: "There is another {relationshipType} relationship between {relatedClientName} and {clientName} ending on {relationshipEnding}. Please review and adjust the dates to track this relationship in one record.";

package/dist/validation/features/client-relationships-common.validation-messages.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"client-relationships-common.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-relationships-common.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,2BAA2B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoE9B,CAAC"}
+{"version":3,"file":"client-relationships-common.validation-messages.d.ts","sourceRoot":"","sources":["../../../src/validation/features/client-relationships-common.validation-messages.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,2BAA2B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsE9B,CAAC"}

package/dist/validation/features/client-relationships-common.validation-messages.js

@@ -4,12 +4,12 @@ exports.CLIENT_RELATIONSHIPS_COMMON = void 0;
 exports.CLIENT_RELATIONSHIPS_COMMON = {
     CURRENT_CLIENT_CANNOT_BE_RELATED_TO_CURRENT_CLIENT: {
         message: `A client cannot have a relationship with itself.`,
-        affectedFields: ['relatedClientId'],
+        affectedFields: ['relatedClient'],
     },
     INVALID_RELATIONSHIP_TYPE_FOR_ENTITY_TYPE: {
         message: `{clientName} is a/an {entityType}, which can't have {relationshipType}s. Please update the relationship type.`,
         params: ['clientName', 'entityType', 'relationshipType'],
-        affectedFields: ['relationshipTypeId'],
+        affectedFields: ['relationshipType'],
     },
     STARTING_DATE_BEFORE_CLIENT_DATE_ESTABLISHED: {
         message: `This relationship's start date cannot be before {clientName}'s date established, {clientDateEstablished}. Please adjust the dates to proceed.`,
@@ -37,32 +37,34 @@ exports.CLIENT_RELATIONSHIPS_COMMON = {
         affectedFields: ['endingDate'],
     },
     ENDING_DATE_AFTER_CLIENT_CLOSE_DATE: {
-        message: `Please update the relationship ending date to be on or before the client's close date, {clientCloseDate}.`,
-        params: ['clientCloseDate'],
+        message: `{clientName}'s close date is {clientCloseDate}. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before {clientCloseDate}: {relationshipsWithEndingDateAfterCloseDate}, or update {clientName}'s close date.`,
+        params: ['clientName', 'clientCloseDate', 'relationshipsWithEndingDateAfterCloseDate'],
         affectedFields: ['endingDate'],
     },
     ENDING_DATE_AFTER_RELATED_CLIENT_CLOSE_DATE: {
-        message: `Please update the relationship ending date to be on or before {relatedClientName}'s close date, {relatedClientCloseDate}.`,
-        params: ['relatedClientName', 'relatedClientCloseDate'],
+        message: `{relatedClientName}'s close date is {relatedClientCloseDate}. One or more relationships have end dates later than this. Please update the following relationship end dates to be on or before {relatedClientCloseDate}: {relationshipsWithEndingDateAfterCloseDate}, or update {relatedClientName}'s close date.`,
+        params: ['relatedClientName', 'relatedClientCloseDate', 'relationshipsWithEndingDateAfterCloseDate'],
         affectedFields: ['endingDate'],
     },
     FINAL_REQUIRED_WHEN_ENDING_DATE_MATCHES_CLIENT_CLOSE_DATE: {
-        message: `The client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.`,
-        affectedFields: ['final'],
+        message: `The relationship between {clientName} and {relatedClientName} has no end date or is not marked as final. Please update {relatedClientName}'s end date to be on or before {clientName}'s close date of {clientCloseDate}, or mark the relationship as final.`,
+        params: ['clientName', 'relatedClientName', 'clientCloseDate'],
+        affectedFields: ['endingDate', 'final'],
     },
     FINAL_REQUIRED_WHEN_ENDING_DATE_MATCHES_RELATED_CLIENT_CLOSE_DATE: {
-        message: `The related client has a close date that is the same as the relationship ending date, therefore the relationship must be marked as final. Please update the relationship's final status to 'Yes', or adjust the dates.`,
-        affectedFields: ['final'],
+        message: `The relationship between {clientName} and {relatedClientName} has no end date or is not marked as final. Please update {clientName}'s end date to be on or before {relatedClientName}'s close date of {relatedClientCloseDate}, or mark the relationship as final.`,
+        params: ['clientName', 'relatedClientName', 'relatedClientCloseDate'],
+        affectedFields: ['endingDate', 'final'],
     },
     CIRCULAR_RELATIONSHIP_DETECTED: {
         message: `{clientName} is listed as a {relationshipType} of {relatedClientName}, during the same timeframe that {relatedClientName} is listed as a {relationshipType} of {clientName}. Please review the relationship records for both clients and adjust the dates or relationship types to prevent a circular loop.`,
         params: ['clientName', 'relatedClientName', 'relationshipType'],
-        affectedFields: ['relationshipTypeId', 'relatedClientId', 'startingDate', 'endingDate'],
+        affectedFields: ['relationshipType', 'relatedClient', 'startingDate', 'endingDate'],
     },
     CONFLICTING_RELATIONSHIP_TYPES_SAME_TIMEFRAME: {
         message: `{relatedClientName} cannot be associated with {clientName} more than once within the same timeframe. Please ensure there are no conflicting relationships for these clients in this timeframe.`,
         params: ['relatedClientName', 'clientName'],
-        affectedFields: ['relationshipTypeId', 'relatedClientId', 'startingDate', 'endingDate'],
+        affectedFields: ['relationshipType', 'relatedClient', 'startingDate', 'endingDate'],
     },
     CONSECUTIVE_DUPLICATE_RELATIONSHIPS: {
         message: `There is another {relationshipType} relationship between {relatedClientName} and {clientName} ending on {relationshipEnding}. Please review and adjust the dates to track this relationship in one record.`,

package/dist/validation/features/client-relationships-income-sources.validation-messages.d.ts

@@ -2,27 +2,27 @@ export declare const CLIENT_RELATIONSHIPS_INCOME_SOURCES: {
     readonly SUBSIDIARY_CANNOT_HAVE_PARENT: {
         readonly message: "{clientName} cannot have subsidiary relationships since it is filing as a subsidiary under {parentClientName} during this timeframe. Please adjust the timeframe or select a different relationship type.";
         readonly params: readonly ["clientName", "parentClientName"];
-        readonly affectedFields: readonly ["relationshipTypeId", "startingDate", "endingDate"];
+        readonly affectedFields: readonly ["relationshipType", "startingDate", "endingDate"];
     };
     readonly SUBSIDIARY_REQUIRES_FILES_SEPARATELY: {
         readonly message: "A subsidiary relationship can only be added to an entity that files separately. Please update the Sub/Parent status before adding a subsidiary relationship, or choose a different relationship type.";
-        readonly affectedFields: readonly ["relationshipTypeId", "filingTypeId"];
+        readonly affectedFields: readonly ["relationshipType", "filingStatus"];
     };
     readonly SUBSIDIARY_PROFIT_PERCENTAGE_MUST_BE_100: {
         readonly message: "A subsidiary must allocate 100% profit to its parent. Please update the percentage to 100% or change the relationship type.";
-        readonly affectedFields: readonly ["profit", "relationshipTypeId"];
+        readonly affectedFields: readonly ["profit", "relationshipType"];
     };
     readonly SUBSIDIARY_LOSS_PERCENTAGE_MUST_BE_100: {
         readonly message: "A subsidiary must allocate 100% loss to its parent. Please update the percentage to 100% or change the relationship type.";
-        readonly affectedFields: readonly ["loss", "relationshipTypeId"];
+        readonly affectedFields: readonly ["loss", "relationshipType"];
     };
     readonly SUBSIDIARY_CAPITAL_PERCENTAGE_MUST_BE_100: {
         readonly message: "A subsidiary must allocate 100% capital to its parent. Please update the percentage to 100% or change the relationship type.";
-        readonly affectedFields: readonly ["capital", "relationshipTypeId"];
+        readonly affectedFields: readonly ["capital", "relationshipType"];
     };
     readonly SUBSIDIARY_ENTITY_TYPE_MISMATCH: {
         readonly message: "A subsidiary entity must be the same entity type as the client during the relationship's timeframe (besides DBA or LLC subsidiaries). Please select a different relationship type, or update either client's entity type.";
-        readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId"];
+        readonly affectedFields: readonly ["relatedClient", "relationshipType"];
     };
     readonly K1_ISSUER_PROFIT_PERCENTAGE_MUST_BE_GREATER_THAN_0: {
         readonly message: "A K1 issuer must allocate a profit percentage greater than 0%. Please enter a profit percentage, or change Receives K1 to 'No'.";
@@ -51,7 +51,7 @@ export declare const CLIENT_RELATIONSHIPS_INCOME_SOURCES: {
     readonly K1_ISSUER_INVALID_ENTITY_TYPE: {
         readonly message: "{relatedClient} is a/an {entityType}, which cannot issue K1s. Please select a different client or choose a different relationship type.";
         readonly params: readonly ["relatedClient", "entityType"];
-        readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId"];
+        readonly affectedFields: readonly ["relatedClient", "relationshipType"];
     };
     readonly INCOME_SOURCE_TOTAL_PROFIT_PERCENTAGE_EXCEEDS_100: {
         readonly message: "The ownership percentages for {relatedClient}'s profit exceeds 100% for this timeframe. Please update their shareholder percentages so that the total between all owners does not exceed 100%.";

package/dist/validation/features/client-relationships-income-sources.validation-messages.js

@@ -5,27 +5,27 @@ exports.CLIENT_RELATIONSHIPS_INCOME_SOURCES = {
     SUBSIDIARY_CANNOT_HAVE_PARENT: {
         message: `{clientName} cannot have subsidiary relationships since it is filing as a subsidiary under {parentClientName} during this timeframe. Please adjust the timeframe or select a different relationship type.`,
         params: ['clientName', 'parentClientName'],
-        affectedFields: ['relationshipTypeId', 'startingDate', 'endingDate'],
+        affectedFields: ['relationshipType', 'startingDate', 'endingDate'],
     },
     SUBSIDIARY_REQUIRES_FILES_SEPARATELY: {
         message: `A subsidiary relationship can only be added to an entity that files separately. Please update the Sub/Parent status before adding a subsidiary relationship, or choose a different relationship type.`,
-        affectedFields: ['relationshipTypeId', 'filingTypeId'],
+        affectedFields: ['relationshipType', 'filingStatus'],
     },
     SUBSIDIARY_PROFIT_PERCENTAGE_MUST_BE_100: {
         message: `A subsidiary must allocate 100% profit to its parent. Please update the percentage to 100% or change the relationship type.`,
-        affectedFields: ['profit', 'relationshipTypeId'],
+        affectedFields: ['profit', 'relationshipType'],
     },
     SUBSIDIARY_LOSS_PERCENTAGE_MUST_BE_100: {
         message: `A subsidiary must allocate 100% loss to its parent. Please update the percentage to 100% or change the relationship type.`,
-        affectedFields: ['loss', 'relationshipTypeId'],
+        affectedFields: ['loss', 'relationshipType'],
     },
     SUBSIDIARY_CAPITAL_PERCENTAGE_MUST_BE_100: {
         message: `A subsidiary must allocate 100% capital to its parent. Please update the percentage to 100% or change the relationship type.`,
-        affectedFields: ['capital', 'relationshipTypeId'],
+        affectedFields: ['capital', 'relationshipType'],
     },
     SUBSIDIARY_ENTITY_TYPE_MISMATCH: {
         message: `A subsidiary entity must be the same entity type as the client during the relationship's timeframe (besides DBA or LLC subsidiaries). Please select a different relationship type, or update either client's entity type.`,
-        affectedFields: ['relatedClientId', 'relationshipTypeId'],
+        affectedFields: ['relatedClient', 'relationshipType'],
     },
     K1_ISSUER_PROFIT_PERCENTAGE_MUST_BE_GREATER_THAN_0: {
         message: `A K1 issuer must allocate a profit percentage greater than 0%. Please enter a profit percentage, or change Receives K1 to 'No'.`,
@@ -54,7 +54,7 @@ exports.CLIENT_RELATIONSHIPS_INCOME_SOURCES = {
     K1_ISSUER_INVALID_ENTITY_TYPE: {
         message: `{relatedClient} is a/an {entityType}, which cannot issue K1s. Please select a different client or choose a different relationship type.`,
         params: ['relatedClient', 'entityType'],
-        affectedFields: ['relatedClientId', 'relationshipTypeId'],
+        affectedFields: ['relatedClient', 'relationshipType'],
     },
     INCOME_SOURCE_TOTAL_PROFIT_PERCENTAGE_EXCEEDS_100: {
         message: `The ownership percentages for {relatedClient}'s profit exceeds 100% for this timeframe. Please update their shareholder percentages so that the total between all owners does not exceed 100%.`,

package/dist/validation/features/client-relationships-owners.validation-messages.d.ts

@@ -1,7 +1,7 @@
 export declare const CLIENT_RELATIONSHIPS_OWNERS: {
     readonly PARENT_RELATIONSHIP_REQUIRES_FILES_UNDER_PARENT: {
         readonly message: "A Parent relationship can only be added to an entity that files under parent. Please update the Sub/Parent status before adding a parent relationship, or choose a different relationship type.";
-        readonly affectedFields: readonly ["relationshipTypeId", "filingTypeId"];
+        readonly affectedFields: readonly ["relationshipType", "filingStatus"];
     };
     readonly MULTIPLE_ACTIVE_PARENT_RELATIONSHIPS: {
         readonly message: "All parent relationships besides the current one must have an ending date. Please add an ending date for any parent relationships that are no longer current, before adding this parent relationship.";
@@ -10,28 +10,28 @@ export declare const CLIENT_RELATIONSHIPS_OWNERS: {
     readonly MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
         readonly message: "There can only be one parent relationship associated to a client during the same timeframe. There is a current parent relationship with {parentRelatedClientName} starting {relationshipStarting}. Please add an end date to that relationship before adding a new one.";
         readonly params: readonly ["parentRelatedClientName", "relationshipStarting"];
-        readonly affectedFields: readonly ["relationshipTypeId", "startingDate"];
+        readonly affectedFields: readonly ["relationshipType", "startingDate"];
     };
     readonly PARENT_CANNOT_BE_SUB_ENTITY: {
         readonly message: "{relatedClientName} cannot be the parent of {clientName}, since it is filing as a sub-entity under another parent during this timeframe. Please adjust the timeframe or select a different relationship type.";
         readonly params: readonly ["relatedClientName", "clientName"];
-        readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId", "startingDate", "endingDate"];
+        readonly affectedFields: readonly ["relatedClient", "relationshipType", "startingDate", "endingDate"];
     };
     readonly PARENT_ENTITY_TYPE_MISMATCH: {
         readonly message: "A parent entity must be the same entity type as the client during the relationship's timeframe. Please select a different relationship type or update either client's entity type.";
-        readonly affectedFields: readonly ["relatedClientId", "relationshipTypeId"];
+        readonly affectedFields: readonly ["relatedClient", "relationshipType"];
     };
     readonly PARENT_PROFIT_PERCENTAGE_MUST_BE_100: {
         readonly message: "A parent must own a profit percentage of 100%. Please update the percentage to 100% or change the relationship type.";
-        readonly affectedFields: readonly ["profit", "relationshipTypeId"];
+        readonly affectedFields: readonly ["profit", "relationshipType"];
     };
     readonly PARENT_LOSS_PERCENTAGE_MUST_BE_100: {
         readonly message: "A parent must own a loss percentage of 100%. Please update the percentage to 100% or change the relationship type.";
-        readonly affectedFields: readonly ["loss", "relationshipTypeId"];
+        readonly affectedFields: readonly ["loss", "relationshipType"];
     };
     readonly PARENT_CAPITAL_PERCENTAGE_MUST_BE_100: {
         readonly message: "A parent must own a capital percentage of 100%. Please update the percentage to 100% or change the relationship type.";
-        readonly affectedFields: readonly ["capital", "relationshipTypeId"];
+        readonly affectedFields: readonly ["capital", "relationshipType"];
     };
     readonly SHAREHOLDER_K1_PROFIT_PERCENTAGE_MUST_BE_GREATER_THAN_0: {
         readonly message: "A shareholder relationship that issues a K1 must have a profit percentage greater than 0%. Please enter a profit percentage, or change Issues K1 to 'No'.";

package/dist/validation/features/client-relationships-owners.validation-messages.js

@@ -4,7 +4,7 @@ exports.CLIENT_RELATIONSHIPS_OWNERS = void 0;
 exports.CLIENT_RELATIONSHIPS_OWNERS = {
     PARENT_RELATIONSHIP_REQUIRES_FILES_UNDER_PARENT: {
         message: `A Parent relationship can only be added to an entity that files under parent. Please update the Sub/Parent status before adding a parent relationship, or choose a different relationship type.`,
-        affectedFields: ['relationshipTypeId', 'filingTypeId'],
+        affectedFields: ['relationshipType', 'filingStatus'],
     },
     MULTIPLE_ACTIVE_PARENT_RELATIONSHIPS: {
         message: `All parent relationships besides the current one must have an ending date. Please add an ending date for any parent relationships that are no longer current, before adding this parent relationship.`,
@@ -13,28 +13,28 @@ exports.CLIENT_RELATIONSHIPS_OWNERS = {
     MULTIPLE_PARENT_RELATIONSHIPS_SAME_TIMEFRAME: {
         message: `There can only be one parent relationship associated to a client during the same timeframe. There is a current parent relationship with {parentRelatedClientName} starting {relationshipStarting}. Please add an end date to that relationship before adding a new one.`,
         params: ['parentRelatedClientName', 'relationshipStarting'],
-        affectedFields: ['relationshipTypeId', 'startingDate'],
+        affectedFields: ['relationshipType', 'startingDate'],
     },
     PARENT_CANNOT_BE_SUB_ENTITY: {
         message: `{relatedClientName} cannot be the parent of {clientName}, since it is filing as a sub-entity under another parent during this timeframe. Please adjust the timeframe or select a different relationship type.`,
         params: ['relatedClientName', 'clientName'],
-        affectedFields: ['relatedClientId', 'relationshipTypeId', 'startingDate', 'endingDate'],
+        affectedFields: ['relatedClient', 'relationshipType', 'startingDate', 'endingDate'],
     },
     PARENT_ENTITY_TYPE_MISMATCH: {
         message: `A parent entity must be the same entity type as the client during the relationship's timeframe. Please select a different relationship type or update either client's entity type.`,
-        affectedFields: ['relatedClientId', 'relationshipTypeId'],
+        affectedFields: ['relatedClient', 'relationshipType'],
     },
     PARENT_PROFIT_PERCENTAGE_MUST_BE_100: {
         message: `A parent must own a profit percentage of 100%. Please update the percentage to 100% or change the relationship type.`,
-        affectedFields: ['profit', 'relationshipTypeId'],
+        affectedFields: ['profit', 'relationshipType'],
     },
     PARENT_LOSS_PERCENTAGE_MUST_BE_100: {
         message: `A parent must own a loss percentage of 100%. Please update the percentage to 100% or change the relationship type.`,
-        affectedFields: ['loss', 'relationshipTypeId'],
+        affectedFields: ['loss', 'relationshipType'],
     },
     PARENT_CAPITAL_PERCENTAGE_MUST_BE_100: {
         message: `A parent must own a capital percentage of 100%. Please update the percentage to 100% or change the relationship type.`,
-        affectedFields: ['capital', 'relationshipTypeId'],
+        affectedFields: ['capital', 'relationshipType'],
     },
     SHAREHOLDER_K1_PROFIT_PERCENTAGE_MUST_BE_GREATER_THAN_0: {
         message: `A shareholder relationship that issues a K1 must have a profit percentage greater than 0%. Please enter a profit percentage, or change Issues K1 to 'No'.`,

package/dist/validation/features/filing-categories.validation-messages.d.ts

@@ -11,7 +11,7 @@ export declare const FILING_CATEGORIES: {
     readonly NAME_ALREADY_EXISTS: {
         readonly message: "Filing category with the same name '{name}' already exists";
         readonly params: readonly ["name"];
-        readonly affectedFields: readonly ["name"];
+        readonly affectedFields: readonly ["filingCategory"];
     };
     readonly OPTION_IN_USE: {
         readonly message: "This option is currently in use and cannot be deleted.";

package/dist/validation/features/filing-categories.validation-messages.js

@@ -14,7 +14,7 @@ exports.FILING_CATEGORIES = {
     NAME_ALREADY_EXISTS: {
         message: `Filing category with the same name '{name}' already exists`,
         params: ['name'],
-        affectedFields: ['name'],
+        affectedFields: ['filingCategory'],
     },
     OPTION_IN_USE: {
         message: `This option is currently in use and cannot be deleted.`,

package/dist/validation/features/roles-and-permissions.validation-messages.d.ts

@@ -21,7 +21,7 @@ export declare const ROLES_AND_PERMISSIONS: {
     readonly PERMISSION_DOES_NOT_EXIST: {
         readonly message: "Permission does not exist";
         readonly params: readonly ["permissionId"];
-        readonly affectedFields: readonly ["permissionId"];
+        readonly affectedFields: readonly ["permissionIds"];
     };
     readonly ROLE_HAS_ASSIGNED_USERS: {
         readonly message: "Cannot delete role with name '{roleName}' because it has users assigned to it";

package/dist/validation/features/roles-and-permissions.validation-messages.js

@@ -24,7 +24,7 @@ exports.ROLES_AND_PERMISSIONS = {
     PERMISSION_DOES_NOT_EXIST: {
         message: `Permission does not exist`,
         params: ['permissionId'],
-        affectedFields: ['permissionId'],
+        affectedFields: ['permissionIds'],
     },
     ROLE_HAS_ASSIGNED_USERS: {
         message: `Cannot delete role with name '{roleName}' because it has users assigned to it`,

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

@@ -16,7 +16,7 @@ export declare const STATES: {
     readonly STATE_TYPE_ID_DOES_NOT_EXIST: {
         readonly message: "State type does not exist";
         readonly params: readonly ["id"];
-        readonly affectedFields: readonly ["stateTypeId"];
+        readonly affectedFields: readonly ["stateType"];
     };
     readonly IS_PARENT_OF_OTHER_STATES: {
         readonly message: "This option is currently in use and cannot be deleted.";
@@ -25,21 +25,21 @@ export declare const STATES: {
     readonly PARENT_ID_DOES_NOT_EXIST: {
         readonly message: "Parent state does not exist";
         readonly params: readonly ["id"];
-        readonly affectedFields: readonly ["parentId"];
+        readonly affectedFields: readonly ["parent"];
     };
     readonly NATION_PARENT_TYPE_NOT_ALLOWED: {
         readonly message: "Nation cannot have associated parent.";
-        readonly affectedFields: readonly ["parentId"];
+        readonly affectedFields: readonly ["parent"];
     };
     readonly STATE_PARENT_TYPE_NOT_ALLOWED: {
         readonly message: "There must be a nation associated with the state '{stateName}'. Please select a nation to proceed.";
         readonly params: readonly ["stateName"];
-        readonly affectedFields: readonly ["parentId"];
+        readonly affectedFields: readonly ["parent"];
     };
     readonly CITY_PARENT_TYPE_NOT_ALLOWED: {
         readonly message: "There must be a state associated with the city '{cityName}'. Please select a state to proceed.";
         readonly params: readonly ["cityName"];
-        readonly affectedFields: readonly ["parentId"];
+        readonly affectedFields: readonly ["parent"];
     };
     readonly OPTION_IN_USE: {
         readonly message: "This option is currently in use and cannot be deleted.";

package/dist/validation/features/states.validation-messages.js

@@ -19,7 +19,7 @@ exports.STATES = {
     STATE_TYPE_ID_DOES_NOT_EXIST: {
         message: `State type does not exist`,
         params: ['id'],
-        affectedFields: ['stateTypeId'],
+        affectedFields: ['stateType'],
     },
     IS_PARENT_OF_OTHER_STATES: {
         message: `This option is currently in use and cannot be deleted.`,
@@ -28,21 +28,21 @@ exports.STATES = {
     PARENT_ID_DOES_NOT_EXIST: {
         message: `Parent state does not exist`,
         params: ['id'],
-        affectedFields: ['parentId'],
+        affectedFields: ['parent'],
     },
     NATION_PARENT_TYPE_NOT_ALLOWED: {
         message: `Nation cannot have associated parent.`,
-        affectedFields: ['parentId'],
+        affectedFields: ['parent'],
     },
     STATE_PARENT_TYPE_NOT_ALLOWED: {
         message: `There must be a nation associated with the state '{stateName}'. Please select a nation to proceed.`,
         params: ['stateName'],
-        affectedFields: ['parentId'],
+        affectedFields: ['parent'],
     },
     CITY_PARENT_TYPE_NOT_ALLOWED: {
         message: `There must be a state associated with the city '{cityName}'. Please select a state to proceed.`,
         params: ['cityName'],
-        affectedFields: ['parentId'],
+        affectedFields: ['parent'],
     },
     OPTION_IN_USE: {
         message: `This option is currently in use and cannot be deleted.`,