Forum Discussion
JSON Formatting
Check whether date B is included in the affected view. SharePoint column-formatting JSON can reference another column, but that column needs to be available in the same view.
Your symptoms fit this: All items includes B, so the calculation stops correctly. The other view may omit B, causing the formatting to treat it as empty and keep counting from A—even though the saved record is correct.
Open the affected view’s Show/hide columns or Edit current view, add both A and B, save, and reload the page. Make sure any other columns referenced by the JSON are included too.
Also check that the JSON references the columns’ internal names, which may differ from their display names.
I wouldn’t change backend configuration or rebuild an index based on this alone. If adding B doesn’t fix it, share the JSON and the column selections for both views; that comparison is the next useful step.