Axiom ValueBoxes do not inherit a selectable time range merely because they are embedded in a grid or panel. Based on the available evidence, use an Axiom Script to pass a Date Time Picker selection to each ValueBox aggregate configuration.
Identify the Time-Range Constraint
A ValueBox can display aggregate results such as start, maximum, minimum, and delta when its start time and period are preallocated. The unresolved requirement is allowing the operator to change that range at runtime.
| Behavior | Evidence status | Engineering decision |
|---|---|---|
| Fixed aggregate start time and period | Confirmed | Use when the reporting interval does not change. |
| Date Time Picker updates ValueBox Aggregate StartTime | Confirmed | Use an Axiom Script to transfer the selected time. |
| Grid or panel propagates its range to contained ValueBoxes | Not demonstrated | Configure the ValueBoxes explicitly instead of relying on containment. |
| Picker automatically supplies both end time and aggregate period | Not established | Verify the required property mapping before implementing a complete range selector. |
Apply the Selected Start Time
The evidence supports updating a ValueBox Aggregate StartTime from a Date Time Picker. It does not provide exact script syntax, component identifiers, or a confirmed property for the selected end time, so those details must be taken from the actual Axiom display configuration.
- Add or identify the Date Time Picker that the operator will use.
- Create an Axiom Script that reads the selected date and time.
- Write that value to the Aggregate StartTime of each affected ValueBox.
- Retain the existing aggregate selection—start, maximum, minimum, or delta—required for each run-hour display.
Handle Multiple ValueBoxes and the End of the Range
For several devices, centralize the selected start time in the picker or a shared display variable, then apply it to every ValueBox through the script. This keeps the controls synchronized without assuming that a parent grid or panel propagates aggregate attributes.
A start time alone does not define a complete interval. The aggregate also needs a period or an equivalent end-time mapping. Because the evidence confirms only the Aggregate StartTime update, inspect the configured aggregate properties and determine whether the picker’s end value can set the period directly or whether the script must derive the period from the selected start and end. Do not assume the trend picker automatically controls ValueBoxes.
Verify the Runtime Result
Select a known start time, trigger the script, and confirm that every ValueBox Aggregate StartTime changes to the same selection. Then change the range and verify that each displayed aggregate refreshes. For a run-hour delta, compare the displayed result with the recorded run-hour values at the chosen interval boundaries; if the start changes but the interval does not, the missing period or end-time mapping remains the fault.
FAQ
Can an Axiom Date Time Picker control a ValueBox?
Yes. The available evidence confirms that an Axiom Script can update a ValueBox Aggregate StartTime from a Date Time Picker.
Do Axiom ValueBoxes inherit the date range from a grid or panel?
That behavior is not demonstrated. Configure the aggregate properties for each ValueBox explicitly or update them together through a shared script.
Why does changing Aggregate StartTime not produce the requested run-hour range?
The aggregate also requires a period or equivalent end-time definition. Verify that the selected end value updates that property; the evidence confirms only the Aggregate StartTime mapping.