Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
DYNAMICS 365 (CRM) - Business Process Flow cannot move to next stage when entering 0 in a whole number or monetary field RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hello,

    When entering 0 (zero) in a whole number or $ field it does not allow me to move to the next stage. I can save but not move to the next stage. The fields are mandatory and zero should be a valid number. Is this a but on Dynamics 365?

    Friday, February 10, 2017 6:52 AM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Hawie-

    The best thing to do at this point would be to log a support case with Microsoft.

    You can also log it to Microsoft Connect here:

    https://connect.microsoft.com/

    • Proposed as answer by Pete Majer Tuesday, March 21, 2017 2:46 PM
    • Marked as answer by Donna EdwardsMVP Monday, April 17, 2017 7:42 PM
    Tuesday, March 21, 2017 2:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If it is a bug, log it with Support.  The CRM Ideas site is for suggestions. <cite>https://crmideas.dynamics.com/ideas</cite>

    Use the "Vote" option if the reply was helpful and "Answer" option if it answered your question. Thank you for helping others find helpful and answered posts!

    Monday, April 17, 2017 7:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    If you make this field not required in the BPF, does it allow you to move to the next stage? Trying to pinpoint if it is indeed the fact that it doesn't recognize a 0 because as you said, 0 is a valid number.
    Tuesday, February 28, 2017 2:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Apologies for the late response.

    I can indeed confirm that when you set this to not required it can move to the next stage.

    Monday, March 20, 2017 4:52 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Hawie,

    It looks like a bug for me too. I tested the same in CRM 2016 and it behaves differently. There Zero is considered as a valid value. But in Dynamics 365 it is not!

    Thanks

    Sachith Chandrasiri

    Monday, March 20, 2017 11:55 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi Hawie-

    The best thing to do at this point would be to log a support case with Microsoft.

    You can also log it to Microsoft Connect here:

    https://connect.microsoft.com/

    • Proposed as answer by Pete Majer Tuesday, March 21, 2017 2:46 PM
    • Marked as answer by Donna EdwardsMVP Monday, April 17, 2017 7:42 PM
    Tuesday, March 21, 2017 2:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If it is a bug, log it with Support.  The CRM Ideas site is for suggestions. <cite>https://crmideas.dynamics.com/ideas</cite>

    Use the "Vote" option if the reply was helpful and "Answer" option if it answered your question. Thank you for helping others find helpful and answered posts!

    Monday, April 17, 2017 7:42 PM