Module · Data✅Knowledge checkCheck: getting at the data4 questions · Pass at 60%1. You hand-edit final_sql on a SQL Builder node. What changes?Nothing — the pickers and the SQL stay in step in both directionsis_customized flips, and the pickers above become decorationThe node turns read-only and must be replaced to change againYour edit is discarded the next time the workflow is saved2. Why should an UPDATE to a CRM record go through CRM Manager rather than a Database Query in write mode?Write mode is measurably slower for single-row changesWrite mode cannot read templates, so no value can be dynamicIt bypasses database triggers, the vector index and the auditWrite mode rejects any statement against a table the CRM owns3. You store this contact's email in a global variable. Two runs happen at the same time. What goes wrong?The second run is queued until the first one releases the variableNothing goes wrong — globals are namespaced per executionThe variable is unreadable to the second run, which sees nothingThey overwrite each other, and it looks like a CRM problem4. You need a value from the trigger inside a Database Query's SQL. What is the right way to put it there?Bind it through parameters rather than into the statementPaste the reference into the query; templates resolve before it runsStore it in a global variable first, then read that in the SQLAssemble the whole statement in a Custom Function and pass it inCheck answers← Back to Logic & Data
