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
7 months agoHobert
7 months agoBrittni
7 months agoBen
7 months agoAshley
6 months agoBernardo
6 months agoCorrina
7 months agoArlie
7 months agoVal
6 months agoDalene
6 months agoElena
7 months agoStevie
7 months agoLeatha
7 months agoRosalia
7 months agoPhyliss
7 months agoFrederick
8 months agoHana
8 months agoVi
8 months agoSommer
7 months agoSommer
8 months ago