Converting visualizations from one type to another

The following list describes the conversion process.

• Data items are mapped to fields with the same name.
• If no field with the same name exists, the first field of the same type is used. Value fields are mapped to value fields. Category fields are mapped to category fields. Category fields that are ID fields are only mapped to other category fields that are also ID fields.
• In active reports, for visualizations that are rendered on the client, extra values and category items are used to fill any empty fields in the converted visualization.

  If you convert to a visualization that has fewer fields than the original visualization, the extra data items are kept as extra values or category items.

• Common properties that are not specific to visualizations, such as Data format, are preserved.
• No warnings appear for properties that are dropped during the conversion.

When you convert a visualization to a new visualization type, you can preserve properties that have the same ID and the same type. Or you can choose to use only the default properties of the new visualization.

If you convert a visualization to a visualization type that has more fields than the original visualization, you must populate the empty fields in the converted visualization. For example, if you convert a column chart to a combination chart that has columns and lines, there are empty fields for the line data container.

You cannot convert a visualization to a current default chart and vice versa.