I think the issue is a bug, there’s something different about the shared parameter that isn’t being accounted for. If it’s an easy fix it will go into a daily build this week. We’ll post back here with more info once available.
When you set a number to a number parameter & then try and remove the number to not make it 0. It wont reset back to Null.
So if you dont set a number into a number parameter it will show empty till you set a number to the parameter.
On the left a number was set and then removed and now it is forced to be 0 but we would like to see this empty not set to zero. To be forced to be set Null.
On the right parameter in the schedule no number was yet set to the parameter, which is null in RIR.