We’re attempting to upgrade our Rally instance from 2023 to rally-sa and the upgrade wizard is failing during the compliance validation phase. The process halts at approximately 73% completion with validation errors related to custom field definitions.
The error log shows:
<ValidationError code="FIELD_MAP_003">
<field>c_RiskScore</field>
<message>Custom field mapping incompatible with target schema</message>
</ValidationError>
We have several custom fields for compliance tracking (c_RiskScore, c_ComplianceStatus, c_AuditDate) that were created in 2023. The upgrade wizard’s validation rules appear to be rejecting our custom field mapping configuration during schema migration. This is blocking our entire upgrade process and we need to maintain these fields for regulatory requirements. Has anyone encountered similar custom field mapping issues during rally-sa upgrades?
I worked through this migration successfully three months ago. Here’s the complete resolution:
Custom Field Mapping: The rally-sa upgrade wizard requires explicit field mapping declarations for any custom fields with validation rules. Your c_RiskScore field needs a mapping definition file:
<FieldMapping source="c_RiskScore" target="c_RiskScore">
<Type>Decimal</Type>
<ValidationRule>value >= 0 AND value <= 100</ValidationRule>
</FieldMapping>
Schema Migration Steps:
Export all custom field definitions from your 2023 instance using the field export utility
Review each field’s validation rules against rally-sa’s allowed syntax (the validation rule format changed - use AND/OR instead of && ||)
Create field mapping declarations for fields with validation rules or dropdown constraints
Update any dropdown values that contain special characters - rally-sa rejects values with pipes, brackets, or certain Unicode characters
Place mapping files in the upgrade wizard’s configuration directory before restarting the validation phase
Validation Rules: The key issue is that rally-sa’s validation engine is stricter about expression syntax. Your validation rules need to use the new expression format. If you have calculated fields or cross-field dependencies, those require explicit dependency declarations in the mapping file.
Upgrade Wizard Configuration: Before rerunning the upgrade, set the validation mode to ‘detailed’ in the wizard config. This will generate a comprehensive report showing exactly which field mappings are failing and why. The report includes suggested corrections for most common issues.
After following these steps, our upgrade completed successfully with all compliance fields preserved. The schema migration process took about 2 hours for 850+ custom fields once the mappings were corrected. Make sure to backup your field definitions before making changes.
Good point. I checked and c_RiskScore is defined as a custom decimal field with range validation (0-100). The c_ComplianceStatus uses a dropdown with values that were valid in 2023. Could the dropdown value definitions be causing the schema migration failure? We have about 15 compliance-related custom fields total, and the upgrade wizard doesn’t specify which ones are problematic beyond c_RiskScore in the error.
We had this exact issue last quarter. The problem is that rally-sa enforces stricter type constraints on custom fields during schema migration. Fields created in 2023 may have attributes that are no longer supported. You’ll need to create a field mapping compatibility report before the upgrade. Check if your validation rules use deprecated syntax or if dropdown values contain special characters that aren’t allowed in the new schema.
The FIELD_MAP_003 error typically indicates that your custom field attributes don’t align with the target schema requirements in rally-sa. Decimal fields with validation rules sometimes need adjustment because the validation rule syntax changed between versions. Before running the upgrade wizard again, you should export your custom field definitions and review them against the rally-sa field schema documentation. Look specifically at validation rule expressions and allowed value constraints. The schema migration process in rally-sa is more strict about data type consistency.
Another thing - check if your custom fields have dependencies on other fields or calculated values. Rally-sa’s validation rules examine the entire field dependency chain during upgrade. If c_RiskScore is used in any formulas or workflow rules, those need to be compatible too. The upgrade wizard validates the complete field mapping context, not just individual field definitions.
I’ve seen this before. The rally-sa version has stricter validation rules for custom field definitions. Your field naming convention with the c_ prefix might be triggering schema compatibility checks. Can you verify if these custom fields have proper type definitions in your current instance? Also check if any of them reference deprecated field types from 2023.