This content has been marked as final. Show 4 replies
Out of the box data protection will only work on a single string. I'd actually question whether your original criteria will work as you want because LSS is not a unique string among the 3 custom4 members so LSS and LSSG will both get caught and replaced. To make data protection work for multiple values you would have to customise the Data Protection scripting in the adapter export action script.1 person found this helpful
Edited by: SH on May 27, 2013 9:05 PM
You already have an issue from the details you have specified. If you are saving non 'LSS' records, i assume by setting the protection vaue as not equal to 'LSS', then it is going save the 'MI' records, but not the 'LSS' records AND the 'LSSGA' records (It will not save the LSSGA records because it includes the string 'LSS' and that is all the function looks for - it uses the VB Instr function.1 person found this helpful
To save multiple strings from a single location would involve bespoke changes to the adaptor Export script, or revising your metadatanames so that changing the protection value string could cover multiple dimension names as you have with LSS and LSSGA.
Would you have an example of how this gets done within the export script ? I tried creating a new strProtection2 inorder to cater to the second string to be protected, but does not work. Any help is highly appreciated.
Solved. I solved it using the same logic, by adding the second member.