Troubleshooting lookup table issues

When using our plugin in combination with lookup tables, you may occasionally run into issues where pricing doesn’t update or returns incorrect results.

Since lookup tables rely on structured data to calculate prices dynamically, even minor misconfigurations can cause problems. This guide will help you identify common issues.

To make sure your lookup table is correct, all the items below should be checked and corrected:

• When using decimal numbers, make sure you use a dot (.) as decimal separator and not a comma (,).
• Make sure cell A1 contains the table name (see screenshot) and does not contain spaces or strange symbols. Only letters, numbers, and underscores are allowed.
• Make sure all cells in row 1 have a value. For example, this table is wrong. The values of row 2 should be added to row 1 instead.
• Similarly, make sure all cells in column A have a value. For example, this table is wrong. The values of column B should be added to column A instead.
• Similarly, make sure there are no blank cells. Replace blank cells with zeroes.
• Make sure the values in row 1 or column A are exactly as written in your field’s settings of the APF plugin. Make sure they do not contain any spaces before or after the label either.
• Numbers should go from low to high (if applicable). In this example table, notice how column A starts at 100 and ends at 180. Similar, row 1 starts at 200 and goes to 300.
• Make sure your formula looks similar to this: lookuptable(your_table_name; afa4fdb; db26442).
  • The first argument is always your table name. The other arguments refer to ID’s of options created with Advanced Product Fields.
  • Do not prepend your ID’s with the word “field”. Both of these are wrong: [field.db26442] or field.db26442.
  • Use a semicolon (;) to separate formula arguments.

Here is an example of a correct lookup table in Google Sheets.

If this guide was not helpful to fix your issue, please contact us.