








































































































.webp)





















SAP Field Service Management (formerly Coresystems) is a cloud FSM platform for technicians, dispatchers, and managers, with scheduling, mobile, parts, and AI-assisted operations.
Have any questions? We’re here to help You
Data synchronization frequency is configurable based on your requirements. For real-time needs, Makini supports webhook-based synchronization where changes trigger immediate updates. For scheduled syncing, common intervals range from every 15 minutes to daily, depending on data volume and business requirements. The initial sync after connecting a system retrieves historical data based on your configuration—typically 30-90 days of historical records. Subsequent syncs are incremental, retrieving only records created or modified since the last sync. Sync frequency doesn't affect pricing. You can also trigger manual syncs on-demand via API when needed for specific workflows.
Makini's API supports date filtering on most endpoints using query parameters. You can filter by creation date, modification date, or entity-specific date fields like order date or delivery date. Common patterns include modified_after=2024-01-01 to retrieve records updated since a specific date, or relative timestamps like modified_after=2024-01-01T00:00:00Z. For optimal performance, use incremental data retrieval patterns rather than repeatedly fetching all records. The sync status endpoint provides the last sync timestamp, which you can use as the modified_after value for your next query. This approach minimizes data transfer and API load while ensuring you capture all changes.
Connection-specific errors often relate to system configuration, permissions, or connectivity issues. Common scenarios include: the system is offline or unreachable, credentials have expired, API rate limits on the source system, or permission changes in the source system. Use the connection status endpoint to check connection health before making API calls. Implement circuit breaker patterns—if a connection repeatedly fails, temporarily stop making requests to avoid cascading failures. Log connection-specific errors separately to identify problematic connections. When errors occur, check if the issue affects all operations or specific entity types, which helps narrow down permission or configuration issues. For on-premises systems, verify network connectivity and firewall rules. Contact support if connection errors persist, providing the connection ID and affected operations.
Yes, Makini supports multi-region deployments for customers requiring data residency in specific regions or needing high availability across geographies. Each region runs an independent instance of Makini with its own infrastructure, ensuring data remains within the specified region. Multi-region deployments are most common for self-hosted installations where customers want instances in multiple AWS regions or data centers. For cloud deployments, we can discuss region-specific hosting based on your requirements. Multi-region support ensures compliance with data localization regulations and provides geographic redundancy for mission-critical integrations.
