Hello List,
Here is another example of how one of our consultants spared some
cumbersome work (and precious time) by using ARSmarts.
Using normalization and reconciliation, create a reconciliation job with
an Identify action.
Unfortunately, the identification rule is incorrect. As a consequence,
all the CI in my dataset received a newly generated ReconciliationID
instead of receiving the ReconciliationID of my golden dataset.
In order to re-run the job, it is necessary to reset all
ReconciliationIDs to 0 and the ReconciliationStatus to Ready to Merge.
Using ARSmarts Data Manager, it is quite simple to perform a Modify All
operation on the relevant records, as you have access to all the Fields.
Without ARSmarts, you need to make the ReconciliationID field visible
using the DevStudio. If you use the Overlay feature, you need to create
an Overlay for the View, and an Overlay for the Field.
Then wait for the Mid-Tier to re-cache (can you do this during business
hours?).
Then you can perform the Modify All.
Then you delete the Overlay Field and the Overlay View.
Then the Mid-Tier refreshes his cache once again.
So it is certainly not impossible without ARSmarts, but it is clearly
more cumbersome and can have serious performance impact.
Cheers,
Kaïs.
kais.albas...@arsmarts.com
www.arsmarts.com
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
