RVR-HIBOB-205
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-HIBOB-205
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error "Cannot find proper mappings for received data" with Error Code: RVR-HIBOB-205 is encountered in the Hibob data connector within Rivery. This indicates that there may be an issue with how the data from Hibob is being mapped in the Rivery platform.
- Initial diagnosis suggests a possible misconfiguration in the mapping setup for the received data, likely due to incorrect field mapping or data structure changes from the Hibob source.
Action Steps:
- Review Field and Data Structures: Verify the fields expected by your Rivery pipeline and compare them with the actual fields present in the Hibob data. This can be done through checking the schema or structure of the data being received from Hibob.
- Check Predefined Reports: Ensure that the Hibob API custom report settings align with the required data structures and that all necessary fields are included in the reports. You may refer to Hibob Predefined Reports to understand standard mappings .
- Mapping Configuration: Revisit the Rivery platform to review and correct any misconfigurations in the column mapping settings. If there have been changes in the Hibob's API fields, update the mappings accordingly.
- Switch Loading Modes: Temporarily switch the data loading mode from "Upsert-Merge" to "Overwrite" to ensure successful data execution and accommodate potential changes in metrics and dimensions.
- Reinitialize Mapping: If the above steps do not resolve the issue, consider reinitializing the mapping process within Rivery to clear any existing configurations that might be causing conflicts.
External References:
- For detailed guidance on connecting with Hibob and managing predefined reports, please see Rivery Hibob Documentation.
- Additional guidance on resolving issues related to Rivery's data connectors can be found in the Rivery Documentation.
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?