Hello,
I have got a problem that has started occurring after we updated to Dynamics 365.
In our business process flow we've set a field (COGS in our case) that is a Whole number to required by one of the phases. The problem we have is that we're not allowed to proceed to the next phase if the value of the field is 0. The problem is that 0 in our case is a perfectly valid value and this makes it impossible for the users to proceed to the next phase of the business process flow. In former versions of Dynamics Online this has not been a problem and the was validated and we could proceed to the next stage even though it's value was 0. there any workaround or fix for this? Is this intended beheviour? In my opinion no value should be treated differently than the value being 0.
Here the field in the business process field, as you can see it's set to required.
Here is an image of our sales process. If I try to go to the next stage while the value is still 0, I get an error message that tells me that I have to complete the required steps before I can advance. If i change the value of COGS to 1 however, it lets me proceed.
Here an image of the field settings:
I've already tried making the field Business Required and Optional, neither of which has an effect.
*This post is locked for comments