Posted by Peter Rabenold at Footwise
on 6/16/2008, 3:59 pm
Perhaps someone could confirm what my testing shows to be the case. It appears that the History component of Customer Merging does not poll out to Remotes from Main on its own without re-initializing all remotes for customers.
- running V 8.52 for both RPRO and DVS
- running Customer Revision including about 5 yrs of SA files.
- I'm processing Client.* and SA files (less current month) with DVS on a local Demo RPRO install, then copying back to Main.
- After a few polling cycles, the Remotes show the correct, single customer record of each pair but do not call up the merged, cumulative history correctly (or at all).
- MAIN DOES show both the correct customer and the correctly merged History however.
- All 4 of our Station A Remotes share all customers with MAIN.
I'm assuming triggering Customer Initialization is the way to go at this point but would not mind some confirmation for that - for example, must all Remotes be done in the same polling cycle?
There are about 160,000 customers so there is a reasonable amount of data.
Peter Rabenold from Footwise
Message Thread:
« Back to thread