Hello accoTOOL Team, we are currently experiencing a reproducible issue with accoPLANNING 1.0.87.3 in Power BI and would like to check whether this is a known bug or limitation. We use accoPLANNING for forecast writeback with the following business grain: Product group Month The writeback table is: planning.WB_ForecastFactor Relevant fields: TK kWarengruppe TK MonatKey Forecast-Faktor Amazon EU Forecast-Faktor Webshop+eBay updateDetails updateDate The transaction keys used in the visual are: TK kWarengruppe TK MonatKey Send only keys is enabled. The issue can be reproduced as follows: Only one month is visible in the visual, for example 2026-09. The forecast value is editable. The changed value can be saved successfully. The writeback is written correctly to SQL. As soon as two months are visible at the same time, for example 2026-09 and 2026-10, the forecast cells are no longer editable. When clicking a cell, it is highlighted in yellow, but no input is possible. As soon as the visual is filtered back to a single month, the cell becomes editable again immediately. The values and transaction keys are still resolved correctly when multiple months are displayed. For example: 2026-09 → TK MonatKey = 202609 2026-10 → TK MonatKey = 202610 The forecast values are also displayed correctly and differ by month. We have already checked and ruled out the following: Relationships in the Power BI model are correct. The writeback table is filtered correctly by month and product group. TK MonatKey is unique per cell. TK kWarengruppe is unique per cell. No Cell Lock configuration is defined. No Conditions are defined. Non-writeable measures is empty. The behavior occurs with both Jahr-Monat and MonatKey as the time dimension. The behavior occurs with Month placed in both Columns and Rows. The behavior also occurs with a very simple SUM measure directly on the writeback column. Therefore, the issue does not appear to be caused by our forecast calculation itself. Writeback works correctly as long as only one month is visible. The original measure is: Forecast-Faktor Amazon EU = 100 + COALESCE ( SUM ( 'planning WB_ForecastFactor'[Forecast-Faktor Amazon EU] ), 0 ) For testing, we also used a simple measure: Forecast-Faktor Amazon EU Delta TEST = COALESCE ( SUM ( 'planning WB_ForecastFactor'[Forecast-Faktor Amazon EU] ), 0 ) This simple measure is also not editable when multiple months are visible. A successful writeback with only one month visible looks like this in SQL: TK kWarengruppe = 18 TK MonatKey = 202609 Forecast-Faktor Amazon EU = 5 When multiple months are displayed again, the values are still shown correctly, but input is no longer possible. We also noticed the existing feedback item “Hierarchy for columns does not work”. However, since our issue also occurs when the month is placed in the Rows section, we are not sure whether it is related. Could you please check: whether this behavior is known in version 1.0.87.3, whether multiple periods in the same visual are generally supported as writable cells, and whether there is any required configuration, fix, or workaround available? We can also provide screenshots of the visual configuration and SQL writeback results if needed. Thank you very much. Best regards,
