NexusTrade guides

Append dataset rows and restore a version

Maintain a dataset with explicit append, replace, restore and indicator-cascade behavior.

Choose append or replacement

appendRows merges new signal rows by timestamp, ticker and optional row_id. Generic datasets can use dedupe_key. replaceContent changes the full content and refuses fewer signal points unless allow_shrink intentionally permits the smaller series. An append is not a full replacement.

Update the linked indicator

Signal append and replace operations cascade to the linked custom indicator by default. Declare point_kind and aggregate_period for the new rows. Use exact dataset_id or custom_indicator_id targets rather than guessing a name from prose.

Inspect row counts and availability after the operation. A transport success is not proof that the linked indicator contains the intended series.

Restore a saved version

Use list_datasets to find the exact owned dataset_id and get_dataset to inspect its current samples. Request edits through edit_dataset with appendRows or replaceContent, then read that same dataset again and compare the expected row count and availability. restoreVersion selects a stored dataset version. Review its identity, coverage and downstream use before restoring; it changes current content. Keep the previous and restored version identifiers in your research notes.

These are supported editing operations, not a public data download. Private account datasets are never added to the public SEO catalog.

Continue exploring