Resolution dates are not required for share structure changes per certain filings. There is a validation mismatch currently between the UI and API.
The UI only loads the dates if it matches a filing where it's required but the API is expecting them regardless. Long term fix is to update API validation but this can't be done yet since it will break other current functionality.
Short term/current fix is to include the resolution dates in the share structure payload anytime shareClasses have been changed regardless of file type.
Related: #30846
Resolution dates are not required for share structure changes per certain filings. There is a validation mismatch currently between the UI and API.
The UI only loads the dates if it matches a filing where it's required but the API is expecting them regardless. Long term fix is to update API validation but this can't be done yet since it will break other current functionality.
Short term/current fix is to include the resolution dates in the share structure payload anytime shareClasses have been changed regardless of file type.
Related: #30846