When you try to save a custom field as reportable that has different types across your templates, the following message appears: "Error: DummyTestField is present in the XML template "DummyTemplateTest1", but has been defined with a different data type"
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Go to Provisioning;
- Open "Configure Reportable Custom Fields";
- Save as Text object an custom field that has type="text" in one template and type="picklist" in a different template;
- Try to click on "Save Extended Field Mapping" at the bottom of the page;
- See the error message;
As per the design, we can't have the same custom field with different types across the templates marked as reportable for ad-hoc reporting.
If your purpose by making this custom field reportable is to extract this information to fix these custom fields and turn them all into the same type the suggestion is to create an entirely new custom field for that and not fix the old one. When we have a custom field already create and we change the type for that we can have a lot of different issues in the future when using this field for any process or when using any integration since the table on the database was created with one logic and you're changing it to a different one. We do not support issues on custom fields where the type of the field was changed.
Report, ad-hoc, reporting, configure, reportable, custom, field, map, mapping , KBA , LOD-SF-RCM-REP , Reporting & Analytics, Data Imports & Exports , Problem