Codeunit 20436 "Qlty. Boolean Parsing"
Quality Management · Microsoft.QualityManagement.Utilities
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
Quality Management · Microsoft.QualityManagement.Utilities · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
GetBooleanFor(Input: Text): Boolean: Converts text input to a boolean value using flexible interpretation rules. Treats any positive boolean representation as true, everything else as false. Recognized as TRUE (case-insensitive): - Standard: “Yes”, “Y”, “True”, “T”, “1”, “On” - Quality-specific: “Positive”, “Check”, “Checked”, “Good”, …IsTextValuePositiveBoolean(ValueToCheckIfPositiveBoolean: Text): Boolean: Checks if a text value represents a “positive” or “true-ish” boolean value. IMPORTANT: This does NOT validate whether the text is boolean-like. It ONLY returns true if the text matches a positive boolean representation. Non-boolean text and negative boolean values both return false. Use case: Qualit…IsTextValueNegativeBoolean(ValueToCheckIfNegativeBoolean: Text): Boolean: Checks if text represents a negative/false boolean value. Only returns true for negative boolean representations; does NOT validate if text is boolean-like. Recognized negative values (case-insensitive): - Standard: “No”, “N”, “False”, “F”, “0” - Quality-specific: “Bad”, “Fail”, “Failed”, “Unaccepta…CanTextBeInterpretedAsBooleanIsh(InputText: Text): Boolean: Checks if text can be interpreted as a boolean-like value (positive or negative). Detects whether input looks like a boolean representation, regardless of its value. Returns true if input matches any boolean representation: - Positive: “Yes”, “True”, “Pass”, “Good”, etc. - Negative: “No”, “False”, “…
Called by
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Page 20414 “Qlty. Inspections API” (5 calls:
ChangeItemTracking → GetBooleanFor,CreateMovement → GetBooleanFor,CreateTransferOrder → GetBooleanFor, …) - Codeunit 20410 “Qlty. Result Evaluation” (3 calls:
TryApplyBooleanFilter → CanTextBeInterpretedAsBooleanIsh,ValidateAllowableValuesOnText → CanTextBeInterpretedAsBooleanIsh,ValidateAllowableValuesOnText → GetBooleanFor) - Codeunit 20599 “Qlty. Misc Helpers” (1 call:
GuessDataTypeFromDescriptionAndValue → CanTextBeInterpretedAsBooleanIsh)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Qlty. Boolean Parsing"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.