How can a data module developer ensure that when a user drags an attribute onto a dashboard that the Map visualization is the default?

Question

Options

• AChange the Represents property for the attribute to Geographic location.
• BSet the visualization property to Map.
• CUse the create map wizard.
• DSelect an empty Map visualization then drag this onto the data.

• A
  81% (29)
• B
  3% (1)
• C
  11% (4)
• D
  6% (2)

Explanation

Setting the Represents property to "Geographic location" at the data module level tells the BI system (e.g., IBM Cognos Analytics) to recognize the attribute as geographic data. This metadata flag causes the platform to automatically default to a Map visualization whenever that attribute is dragged onto a dashboard, because the system knows it contains location-based content.

Why the distractors are wrong:

• B – "Set the visualization property to Map" applies to a specific dashboard widget instance, not a reusable default behavior embedded in the data module itself.
• C – The "create map wizard" is a guided UI tool for building a specific map, not a mechanism for setting default visualization behavior for an attribute.
• D – Dragging an empty Map visualization and then dropping data onto it is a manual workaround each time, not a default setting - it defeats the purpose of a "default."

Memory tip: Think of Represents = Recognition. When you tell the data module what the attribute represents (geographic location), the system recognizes it and picks the right visualization (Map) for you automatically. The default lives in the data, not in the dashboard.

No community discussion yet for this question.