Syndication only when records are updated, but ONLY for selected fields

Question

again with one of my : it's that even possible at all ?
the case, we have a customer repository where, among other things we add some extra info (classification ABC and similar mainly) to a small percentage of them (around 5 - 10 %)
and we would like to distribute only those changes, changes in few fields
of course we load plenty of fields from R3 and other systems, and also we modify records to assign the customers to different business organization that have to look after, this assignments change also very often (it can affect to 30 to 40 % of the customers). All this data does not need to be distributed.
so in figures (as example to easier understand), weekly base :
_ 250.000 _ aprox records in MDM
_ __ 1.000 _ new records every week from source systems
_ __ 8.000 _ updated records every week from source systems
_ ______________(yes, big number, some marketing attributes and soft stuff they like to see in MDM)
_ ____ 100 _ aprox are "enhanced" with data we need to distribute
_ __ 50.000 _ aprox records are re-assigned or reclassify with data we do NOT need to distribute
_ ______________(mostly done with assignments and so on that keep changing every week)
so, even selecting "suppress unchanged records", MDM keeps distributing like 60.000 records, when we only need those 100.
is any direct way to make this ??
as a work-around, I have think into a workflow that in a way flags a new field (to_be_distributed) always and only when a user change one of this specific fields. And then filter the distribution for only this field = True. And another workflow that set the mention field to False, just after the distribution is done.
Crazy idea ??, anything better ??
(we are in MDM 5.5, if the solution require 7.0, migration plans are in the horizon)
thanks in advance, everybody

Answer 1

Hi,
       We had the same scenario where in we have to Syndicate only certain Fields to Legacy...As per your scenario add classification data to your Existing Customer repository. Next steps is to create a map for the classifications data...You write your own conditions in FreeForm search of MDM Syndication. Whenever certain conditions are satisfied, MDM system will syndicate. 
Next - Option - If you are implementing work flow then create a extra field called Syndicate_Legacy. Syndicate_Legacy should be Flat LookUps .Values should be Syndicate,No Syndicate.  Before end of the WF, you should have  a assignment step. By using assignment change the value to Syndicate or Not syndicate. For this , along with map you should also write a condition in Free form search in syndicator stating that only if Field(Syndicate_Legacy) = Value(Syndicate). I believe these should solve your issue...If not please let me know...
Thanks
Ganesh Kotti