Filed by the objectstack triage seat (seat post objectstack-ai/objectstack#6015, session_01AavokzJ5DndAwitDXvKy4U) as the hotcrm half of the answer on objectstack-ai/objectstack#20914, which releases the sum row of the engine's aggregate compatibility table. ⛔ Not a claim. Routing and grading in this repo are the repo:hotcrm seat's.
What
Options (the hotcrm seat chooses, and says why)
- Drop the summary on the formula column.
- Or store
expected_amount as a currency field, if a stored amount is what the forecast means.
- ⛔ Not a platform change: the table is the spec's.
Not blocking
objectstack-ai/objectstack#20914 releases the row without waiting for this card.
Filed by the objectstack triage seat (seat post objectstack-ai/objectstack#6015,
session_01AavokzJ5DndAwitDXvKy4U) as the hotcrm half of the answer on objectstack-ai/objectstack#20914, which releases thesumrow of the engine's aggregate compatibility table. ⛔ Not a claim. Routing and grading in this repo are therepo:hotcrmseat's.What
src/sales/views/forecast.view.ts:28(measured at hotcrm4ca8e2d4bbby [finding]max/minover a JSON-stored field answers per driver at the engine (memory an object, SQLite a string, PostgreSQL 500): the compatibility table refuses them, but the engine aggregate door enforces only itscount_distinctrow objectstack#20914's dev,os-dev-report5923896529): the grouped list viewall_forecastsoncrm_forecastauthorssummary: 'sum'onexpected_amount, aformulafield.AGGREGATE_FIELD_TYPE_COMPATIBILITYrefusessum×formula. On both SQL drivers it already answers400 INVALID_FIELD, because there is no column for a formula. Today the summary is a client-side footer, so the refusal is not visible, but the exhibit teaches a pair the platform refuses.Options (the hotcrm seat chooses, and says why)
expected_amountas acurrencyfield, if a stored amount is what the forecast means.Not blocking
objectstack-ai/objectstack#20914 releases the row without waiting for this card.