2830254 - How to enable Server Snapshot Based in SuccessFactors OData API using SAP Cloud Platform Integration CPI

You are running your CPI custom artifact and you are receiving the following error:

• [COE0019][SNP]Snapshot lost for current pagination query, pls relaunch query and start from 1st page, and use session-reuse for snapshot pagination

This KBA has the objective to share one working example to be used by your partner or consulting team implementing the Server Snapshot-Based (paging=snapshot pagination parameter) for the SF OData API.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP SuccessFactors HCM Suite - OData API
• SAP Cloud Platform Integration - CPI / HCI

$paging=snapshot, Enabling session re-use, server side pagination, SAP Cloud Platform Integration - CPI / HCI,  SAP SuccessFactors HCM Suite - OData API, Server Snapshot-Based, [COE0019][SNP]Snapshot lost for current pagination query, pls relaunch query and start from 1st page, and use session-reuse for snapshot pagination, ${property.SF.Receiver1.hasMoreRecords} contains 'true', "Looping Process Call" + "Process in Pages" and "Server Snapshot-Based", Condition Expression, HTTP Session Reuse, On-Exchange, Looping process Call, max number of interactions, Pagination = Server Snapshot-Based, Page Size, Process in pages, $skiptoken, X-SF-Paging: snapshot, Request Header, On Exchange , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-CON , Cloud Platform Integration Adapter (CPI) , LOD-SF-INT-CUS , Boomi & CPI (HCI) Custom Content , LOD-SF-INT-HCI , Standard SF to 3rd Party CPI (HCI) Content , How To