To ensure all tickets from the remote POS databases have made it to the centralized back office and the latest version of each ticket has replicated, it would be nice to have something that runs once a day or as part of the end of day process that...
Chris Wright
about 4 years ago
in Data Replication
3
Future consideration
The current data replication process for deletes creates a sydatrep distribution record for every active location for every detail record when something like a price list for example is deleted. It would be nice to see a method where perhaps just ...
Justin Higdon
over 6 years ago
in Data Replication
2
Future consideration
Ability to replicate Inventory, Production, and Operations data
Currently, replicating inventory, production, and operations data is complex and largely unknown. This ability would allow for some functions to be done remotely while others centrally. For example, production/operations information maintained at ...
Currently, when deleting a record (such as a sales order), the delete will be replicated to all plants, even if replicating based on Location ID. The impact of this is increased DR bandwidth usage.
Right now, the Data Replication process works in a FIFO stack. This generally works well until a site has been down for weekend with the Apex device being offline. This queues up all the changes, but once the site is back up, we are waiting for im...
Logan Van Proyen
about 5 years ago
in Data Replication
2
Future consideration
I would love to see Data Replication move closer to a web API rather than a database function. The main reason is with Data Replication we are not able to utilize Application logic. Our remote sites simply act as a ticketing computer. No orders/di...
Logan Van Proyen
about 4 years ago
in Data Replication
1
Reviewing