Symptom
What would be the impacts of changing the order of the Custom Reportable fields on the instance?
Environment
SAP SuccessFactors Recruiting Management
Resolution
Behind the scenes, the system attributes some IDs into the field that are added into the Reportable Custom Fields, and that id is using on retrieving the information from the field on the database.
It is not advisable to change it, as the fields changed might be in use on some specific areas, which might be impacted:
- Reports: If one of the fields that was involved on the order change is currently in use in a Report, that report might stop working, or might be necessary to execute a sort of a refresh, correcting the fields and re-selecting them on the report itself. As some other reports use the table reference from the instance, those might break as well;
- SFAPI integration: As the SFAPI is based on the Ad-Hoc Data Dictionary, in case there are some reports created to be used via SFAPI, those willl be impacted as well. The idea falls into the same as point 1, as the report might have to be rebuilt, and the fields inside the report will not be properly recognized, which means that when running the SFAPI integration on top of that report, it will also not work.
Keywords
report, custom, reportable, field, change, order, sfapi, reports, column , KBA , LOD-SF-RCM-REP , Reporting & Analytics, Data Imports & Exports , How To
Product
SAP SuccessFactors Recruiting all versions