It would be good if they explained how to use synchronization expressions, user filters in service-based records and APIs to activate synchronization from the origin
📝 Summary of Key Points: The speaker explains that there is a limit of a thousand items that can be synced in one batch when using a Recco type. They provide a solution for syncing more than a thousand items. The speaker demonstrates the process of creating a connected system and an integration rule for a public API from the NHTSA. This API provides information about vehicle identification numbers (VINs) and different car models. They create a record type to display the data from the API and set up a record data source that consumes the integration rule. They enable syncing in batches to overcome the limit of a thousand items. The speaker previews the data in the record type, selects a primary key, and observes the syncing process in the sync history. The final result is the synced data displayed in the record list. 💡 Additional Insights and Observations: 💬 "Syncing in batches" refers to syncing data in smaller groups or chunks to work around the limit of a thousand items. 📊 No specific data or statistics were mentioned in the video. 🌐 The NHTSA is a credible source for vehicle-related information and adds credibility to the process demonstrated in the video. 📣 Concluding Remarks: This video provides a step-by-step guide on how to sync more than a thousand items from a data source using a Recco type. By using a public API from the NHTSA as an example, the speaker demonstrates the process of creating a connected system, setting up an integration rule, and syncing the data in batches to overcome the limit. This information can be valuable for individuals or organizations looking to sync large amounts of data efficiently. Made with Talkbud
Imho you are using in your Integration a really bad practice putting query params in the Relative path instead put them in the Query parameters section
Hi Carlos, thanks for your comment. In larger applications, for better reusability, readability and maintainability it would indeed be better to use the query parameters in the integration object. For this specific and narrow use case, it doesn't really make a difference. To keep those videos focused on one topic, we're not always able to hit on every topic but we hope to produce more content around integrations in the future which cover those best practices.
It would be good if they explained how to use synchronization expressions, user filters in service-based records and APIs to activate synchronization from the origin
Thank you for your suggestions! We will add more integrations-related content.
it would be great if you can share information about how to sync records using process models in batches using identifiers , Record Sync Smart service
Thank you for sharing this idea!
📝 Summary of Key Points:
The speaker explains that there is a limit of a thousand items that can be synced in one batch when using a Recco type. They provide a solution for syncing more than a thousand items.
The speaker demonstrates the process of creating a connected system and an integration rule for a public API from the NHTSA. This API provides information about vehicle identification numbers (VINs) and different car models.
They create a record type to display the data from the API and set up a record data source that consumes the integration rule. They enable syncing in batches to overcome the limit of a thousand items.
The speaker previews the data in the record type, selects a primary key, and observes the syncing process in the sync history.
The final result is the synced data displayed in the record list.
💡 Additional Insights and Observations:
💬 "Syncing in batches" refers to syncing data in smaller groups or chunks to work around the limit of a thousand items.
📊 No specific data or statistics were mentioned in the video.
🌐 The NHTSA is a credible source for vehicle-related information and adds credibility to the process demonstrated in the video.
📣 Concluding Remarks:
This video provides a step-by-step guide on how to sync more than a thousand items from a data source using a Recco type. By using a public API from the NHTSA as an example, the speaker demonstrates the process of creating a connected system, setting up an integration rule, and syncing the data in batches to overcome the limit. This information can be valuable for individuals or organizations looking to sync large amounts of data efficiently.
Made with Talkbud
Imho you are using in your Integration a really bad practice putting query params in the Relative path instead put them in the Query parameters section
Hi Carlos, thanks for your comment. In larger applications, for better reusability, readability and maintainability it would indeed be better to use the query parameters in the integration object. For this specific and narrow use case, it doesn't really make a difference. To keep those videos focused on one topic, we're not always able to hit on every topic but we hope to produce more content around integrations in the future which cover those best practices.