Common Dataset: Trigger “Newly Added Rows” sporadically does not link new sync rows

User Talk Common dataset
1

Title: Common Dataset: Trigger “Newly Added Rows” sporadically does not link new sync rows

Environment

  • SeaTable on-prem (version 5.3.12).

  • QS base with table “Chargen Produktion” based on Common Dataset.

  • Data flow: external SQL DB (external) → Transfer Base (Seatable)→ Common Dataset → QS Base. Sync from SQL every hour.

Setup

  • View “Alle Chargen”: unfiltered.

  • Columns in “Chargen Produktion”:

    • KHK Artikel: type Number, 0 decimal places. Comes from the Transfer Base.

    • Produktnr (link column): linked to table “Produktnr”.

  • Table “Produktnr”:

    • Primary column = product number, unique, no duplicates.

  • Automation:

    • Trigger: Newly Added Rows.

    • Action: Add Links in Produktnr with match KHK Artikel = Produktnr (target table).

Observation

  • Until 17.09. new rows added via CDS were correctly linked.

  • Since 18.09. new rows appear (visible via timestamp KHK Wann), without link being set.

  • Other periodic rules run successfully; only the links for the latest synchronized rows are missing.

Conditions already checked

  • View contains all rows.

  • KHK Artikel and target Produktnr are consistently of type number.

  • Matching entries exist in “Produktnr”, no duplicates.

  • At least one successful sync occurred on 18.09.

Question to SeaTable

  • Does a Common Dataset sync reliably trigger “Newly Added Rows” for newly synchronized rows?

  • If not: under which conditions can a row created or filled in a later sync fail to trigger?

  • Are there known limitations or changes that could explain this behavior since 17.09.?

image
image652×864 23.3 KB

image
image1433×555 55.8 KB

2

I assume that the dtable-events component is in an error state and does not process the auto-linking requests any more. This would explain why it simply stopped working on September 18. Check your log files.

You are saying that you run your own SeaTable Server instance. In this case, whether or not there are changes is a question you must ask yourself/your admin.