I'm not sure about option C) Associate the field with the characteristic In the Open ODS View. It doesn't seem like the most efficient way to achieve the requirement.
I think the correct answers are A) Associate the field with the characteristic in the CompositeProvider and B) Add the characteristic to the DataStore object.
Okay, let's think this through. If it's an existing field-based data flow, then I'd say options A and C are the way to go. Gotta love those LSA++ concepts!
Wait, is this a trick question? I feel like there's a hidden joke here, like option B is actually 'Add the characteristic to the DataStore object (with a unicorn)' or something.
I'm going to go with options A and C. Associating the field with the characteristic in both the CompositeProvider and the Open ODS View should do the trick.
I'm not sure about option C) Associate the field with the characteristic In the Open ODS View. It doesn't seem like the best approach for leveraging a hierarchy.
I think the correct answers are A) Associate the field with the characteristic in the CompositeProvider and B) Add the characteristic to the DataStore object.
Hmm, I think option C looks promising. Associating the field with the characteristic in the Open ODS View seems like a straightforward way to leverage the hierarchy without changing the transformation.
Deandrea
11 months agoHobert
11 months agoBrittni
11 months agoBen
11 months agoAshley
11 months agoBernardo
11 months agoCorrina
11 months agoArlie
12 months agoVal
11 months agoDalene
11 months agoElena
12 months agoStevie
12 months agoLeatha
11 months agoRosalia
11 months agoPhyliss
12 months agoFrederick
12 months agoHana
1 years agoVi
1 years agoSommer
12 months agoSommer
12 months ago