The fetch block in Scribe Online IS advanced maps allows an integration the ability to process records from an additional data set—conceptually, this is similar to a sub query. The fetch block is available for any Connector for any entity that supports reads.
In this podcast, we will discuss use-cases around the fetch block, including the ability to build ad-hoc relationships when a relationship is not exposed through a Scribe Online Connector. Additionally, you’ll learn how to use the fetch block to process all of your data sets that are in scope of the map.
In the sample ADV map blocks to the left, you’ll see a map in Scribe Online that will query “sales order” headers from a source, processing each header record from the result set one-at-a-time. For each header, it will upsert a record to the target application, and then process each of the “sales order line item(s)” from a result set returned by the fetch block.
After all of the fetched line items have been processed, the map will exit the fetch block and continue through the rest of the map—which has currently been left empty.
For users already familiar with Scribe Online Advanced Maps, you can think of the fetch block as a combination of the query and lookup operation blocks.