Forum Discussion
Fabric IQ
Posting this here because I don't know where else to put it.
Issue: Input column with a default value derived from another measure does not accept scenario overrides immediately after scenario creation. The UI reports “Value saved,” but the displayed value does not change. Performing a bulk edit on the Base sheet (e.g., +100 followed by -100) initializes the column, after which scenario overrides work as expected.
I joined another group and posted something similar there. Got a different reaponse:
3 Replies
- Omkar_1712
Solution Specialist
Hello jcotton,
From your description, this doesn't sound like expected behavior.
The key observation is that the override reports "Value saved", but the displayed value doesn't change until a bulk edit (for example, +100 followed by -100) is performed on the Base sheet. That suggests the input column may not be fully initialized or recalculated immediately after the scenario is created.
Since the bulk edit doesn't introduce a lasting data change but does cause subsequent scenario overrides to work correctly, it appears to be triggering a refresh or initialization of the underlying model rather than correcting the data itself.
I couldn't find Microsoft documentation describing this as a known behavior or limitation of Fabric IQ. Based on your reproduction steps, I would recommend:Verify whether the issue occurs with multiple models or only this specific workbook.
Test with a newly created model containing a simple input column that has a default derived from another measure to determine whether the behavior is reproducible.
If the issue is consistently reproducible, open a Microsoft Support ticket or submit feedback, including the exact reproduction steps (new scenario → override → "Value saved" with no visible change → bulk edit → override works). That will help determine whether this is a product defect.
One additional question that may help narrow this down:Does the issue occur only when the default value is derived from another measure, or does it also happen for input columns with a fixed default value?
That distinction could help identify whether the problem is related to dependency evaluation or to scenario initialization.
Microsoft reference:
Fabric IQ documentation:
https://learn.microsoft.com/fabric/fabric-iq/Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community. - jcottonNew Member
I joined another group and posted something similar there. Got a different reaponse:
- v-abhinavmu
Community Support
Hi jcotton,
Thanks for reaching out to the Microsoft Fabric Community forum. and thanks to Omkar_1712 for sharing valuable insights.
Thank you for the update. We're glad to hear you found a workaround and that the scenario functionality is now working as expected. We appreciate you sharing your findings, and thank you for your feedback! Have a great day.