NoSQL
Resolve a shared contact for this pump
BOTIE
Examples, experiments and workspace controls
Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.
Try your own inputs
Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.
Context for this challenge
Connect the extracted supplier_id to the exact directory lookup. Inspect found and value before attaching anything.
The pump has a supplier reference and an old purchase name.
Inspect the component calculation
Look up one exact key(
Keyed records: Current supplier directory
Exact key: Read a document path(
Document: Pump and historical snapshot
Field path: supplier_id
)
)Examples and results
- Current supplier directory
{ "S1": { "phone": "111" } }- Pump and historical snapshot
{ "asset_id": "P1", "supplier_id": "S1", "purchased_name": "Old Pumps" }- Required result
{ "found": true, "value": { "phone": "111" } }
Try a fresh construction
This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.
Stuck? Inspect a worked construction
The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.
Assumptions and test precision
The browser runs an explicit model of the mechanism. It does not connect to MongoDB or Redis, simulate their query planners, or establish their concurrency guarantees. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.
Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.
The referenced supplier is missing
This check uses the pieces from “Attach the directory’s current supplier record”.
BOTIE
- Pump and historical snapshot
{ "asset_id": "P9", "supplier_id": "S9", "purchased_name": "Historic Supplier" }- Current supplier directory
{ "S8": { "phone": "888" } }- Unresolved supplier marker
{ "missing": true }
Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.
Build a construction in the workspace above first. This case will test those pieces.
What would happen if the application labelled a duplicated phone current but never refreshed it?
For every repeated fact, state whether it is a snapshot or a copy that must catch up.
The browser runs an explicit model of the mechanism. It does not connect to MongoDB or Redis, simulate their query planners, or establish their concurrency guarantees.
Work through the Python challenges →