From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 28 of 60
-
Triage Missing References Caused by Import Order
Compare source identities, parent availability, row sequence, and final relationships to distinguish ordering failures from invalid or mismatched references.
-
Prioritize Import Reference-Ordering Problems
Assess order-dependent links by unresolved relationships, silent omissions, affected source workflows, and the reliability of supported recovery or ordering guidance.
-
Investigate Order-Dependent References in Imports
Trace parent acceptance, dependent lookup, identity matching, and deferred resolution using the same related records in different source orders.
-
Verify Reference Resolution Across Import Orders
Check supported parent-dependent sequences, existing parents, missing references, deferred resolution, and exact final links using a controlled dependency graph.
-
Keep Import Dependency Rules Understandable
Document supported reference order and resolution boundaries, and preserve fixtures that distinguish late parents, missing references, and incorrect identity matches.
-
Triage Misaligned Columns in Multi-File Imports
Compare each file’s header order, selected mapping, source identity, and final values to locate incorrect column alignment across a combined import.
-
Prioritize Column Alignment Defects Across Imports
Assess multi-file alignment problems by silent wrong-field assignments, source-schema variation, preview coverage, and the cost of tracing accepted records back to files.
-
Investigate Schema Alignment in Multi-File Imports
Use reordered, missing-column, and repeated-header files to trace whether combined imports align by name, position, or a per-file mapping contract.
-
Verify Columns Align Correctly Across Imported Files
Check reordered schemas, missing fields, duplicate labels, per-file previews, and exact final destinations in a controlled multi-file import.
-
Keep Multi-File Import Alignment Predictable
Document schema alignment and retain contrasting file layouts so optional fields, reordered columns, and ambiguous labels cannot silently change assignments.
-
Triage Text Length Failures During Import
Compare source length, preview validation, encoding, destination limits, and saved text to locate late rejection or silent truncation of imported fields.
-
Prioritize Import Field Length Defects
Rank text-length problems by silent truncation, late failure, affected fields and scripts, warning quality, and recovery from the original source value.
-
Investigate Conflicting Text Limits in Imports
Trace character and byte measurements, normalization, validation, and destination constraints with values just below, at, and above the intended boundary.
-
Verify Text Length Boundaries Across an Import
Check boundary values, character representations, preview messages, stored text, and correction paths against the field’s documented length rule.
-
Keep Import Text Limits Consistent and Explainable
Document field length units and preserve boundary fixtures so preview, validation, storage, and correction messages continue to agree on accepted text.
-
Triage Whitespace Changes in Imported Values
Compare exact source strings and field-specific normalization rules to distinguish intended trimming, meaningful whitespace loss, and invisible matching differences.
-
Prioritize Whitespace Normalization Defects in Imports
Assess trimming problems by altered identity or formatting, broken matches, affected fields, preview visibility, and recovery from the original source text.
-
Investigate Import Whitespace and Matching Rules
Trace exact strings through trimming, parsing, field assignment, storage, and comparison using field-specific whitespace fixtures with independent expectations.
-
Verify Whitespace Handling Preserves Import Meaning
Check field-specific trimming, meaningful spacing, exact stored strings, and downstream comparisons so cleanup neither breaks matching nor discards intended content.
-
Keep Import Whitespace Rules Field-Specific
Document meaningful spacing and retain exact-string fixtures so future cleanup, storage, or matching changes preserve each imported field’s intended semantics.
-
Triage Unexpected Writes During an Import Preview
Separate expected preview metadata from destination changes and trace whether validation or previewing creates or updates records before execution is confirmed.
-
Prioritize Unintended Import Preview Writes
Assess premature destination changes by unconfirmed work, affected preview paths, user visibility, reconciliation effort, and the reliability of the execution boundary.
-
Investigate Import Preview Side Effects
Trace preview, validation, mapping, and execution operations against a known destination baseline to isolate the first unintended domain write before confirmation.
-
Verify Import Previews Leave Destination Records Unchanged
Check upload, validation, mapping edits, refresh, and cancellation against a known baseline before confirming that explicit execution performs the intended import.
-
Keep Import Preview and Execution Boundaries Separate
Document expected preview bookkeeping and retain state-baseline checks so future validation or navigation changes cannot import destination records before confirmation.