Example error messages
Cannot identify the correspondence of the 'Energy_Type__Native' dimension (with length 7), found in the data being pasted, with an existing index in the model.
Indexes in the copied data don't match the indexes in the destination table. Paste was unable to identify a likely index in your model matching the following dimensions in the incoming data: Active_cases (length 3) Output_year (length 27)
Indexes in the copied data don't match the indexes in the destination table.
You may encounter this error when you try to paste a multi-dimensional table from one Analytica instance to another, or from another application where the multidimensional data is represented using Analytica's Export-Import data format.
When you paste a 4-D table into Analytica, it needs to figure out how the 4 dimensions of the incoming data relate to the indexes of your table or model. To determine this, Analytica looks for matching names, lengths, pivots and naming of index elements. The correspondence algorithm can usually figure out the intended correspondence even when names, pivots and index elements don't match, but it the discrepancies are too great or are ambiguous, then you'll see this error.
The first step is to figure out why it happens. You presumably have an index correspondence in mind. Start by checking the lengths of the indexes. If the lengths don't match, you may have made a mistake in preparing your data. Some variations of this error message will provide information about the incoming dimensions that it was not able to match, so focus on those. Compare the length shown in the error message to the length of the index you think it should match. If there are additional dimensions in the incoming data that are not listed in the error message, it means that it felt confident it had successfully matched those to an existing index.
If the lengths match, are there two dimensions that have the same length? This may have caused an ambiguity. You may be able to solve this by pivoting your table to exactly match the pivot of the incoming data. Failing that, try renaming indexes so that they have the same names as in the incoming data.
If one of the indexes you think should match is not already in your table, add it to the table.
Does either index (in the incoming data, or in your destination table) contain duplicate elements? In general, it is a bad idea to create an index where the same element appears more than once -- this makes operations like Subscript ambiguous. If the first value in a slicer dimension appears again as a duplicate element of the index, the length of the index will be misjudged. The best remedy here is to make the all labels within the index different.