Skip to content
Merge Table Pack
Share
Explore
Merge Table Pack

icon picker
Troubleshooting

Issues that can occur, and how to fix them
megaphone
Changes you make to your docs and tables take time to be seen by the pack. Most issues are caused by this delay, and can be solved by waiting around 10 seconds before refreshing the sync again.

Changes to the source tables not showing up

It usually takes a few seconds for changes you make to any of the tables included to be merged to be reflected when the pack queries the tables. Simply wait around 10 seconds then start the sync again. You might need to stop editing the table (click outside the cell, or column header, or the table entirely) for changes to take effect.

“Unexpected dot operator Could not find <some column name> reference in [Merged Row]” error

This error occurs when the Sync Table is updated after a merged column is no longer returned as a resulting column from the merge, for example after changing the name or deleting a column in one of the source tables, or changing the columnMerge. Since the merged column is no longer returned as part of the merge, this causes the resulting column in the Sync Table to reference a merged column name that no longer exists on the merged rows. Simply delete the broken column, undo the change to the source table(s), or undo the change to the Sync Table configuration that caused this merged column to no longer be returned from the merge.

Merged column in the Sync Table shows values for only some of the rows

This could be expected, for example under columns for a union merged sync table that are not common to all table. If not, this happens when the sync is kicked off in between changes to the doc propagating, which causes an inconsistent state of the table data to be seen by the pack. It is resolved by waiting around 10 seconds then starting the sync again. If the changes would cause that column to no longer be returned as part of the merge, you might then encounter the , see that section for resolving it.

“The table link was not a link to a table” error

This means the table link you provided is not valid. Make sure you are properly copying the table link of the table you are trying to merge, as explained in .

“At least one of the table links is a view table, which prevents the \`sortBy\` parameter being set to "natural" while the \`hiddenColumns\` parameter is enabled. [...]”

This occurs because of the way rows are fetched for view tables when the hiddenColumns parameter is enabled, due to the nature of the pagination across the table rows. The fix (as described in the remainder of the error), is to either change the sortBy parameter to something other than “natural” (for example, “createdOn”), or uncheck the hiddenColumns parameter. Alternatively, remove or replace the view tables altogether.

“You do not have access to the table specified by the table link: [...]”

If you are expecting to have access to the doc that contains the linked table, this can mean that the account that was connected to the pack is not properly granting authorization (an occasional Coda bug). In this case, removing the account connected with the Merge Table (Lite | Pro) pack can fix the issue. To do so, go to , or through the “Settings” tab in the pack menu, then click “Remove this account” for all accounts associated with the pack. The account should be re-connected automatically the next time you use the pack.

“Couldn't find this data in Merge Table (Lite | Pro)” error

This might mean the table link you provided is not valid. If not, this happens when the sync is kicked off shortly after adding said table to the doc, which causes an inconsistent state of the doc data to be seen by the pack. It is resolved by waiting around 10 seconds then starting the sync again.

“Last sync failed” in the sync table, with “Failed to fetch data from Merge Table (Lite | Pro)” or some other red error message in the configuration menu

If you’re seeing this error, it’s probably a mistake on our end.
Please click the link that appears below the error to contact the developer, or reach out directly as detailed in the section.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.